For the diagnostics quickfix, I have ":Telescope diagnostics bufnr=0" (and one without bufnr) mapped. This makes it super easy to filter diagnostics as needed and then Ctrl+Q to send the results to the quickfix list.
Learning NeoVim while learning C doing Advent Of Code. Good for me that you're doing an Advent of Neovim ! For now I'm mostly using it like I used Vim, I haven't configured an LSP or I have one and I don't know how to use the autocomplete and stuff, but anyway it's really fun and interesting. Will keep at it for at least 3 months and I'll see if I ditch VS Code for good (although I never had anything against it beside some slowing up sometimes on personal projects). Thank you for the work !
Some of these mappings (like grr) and other LSP ones were not default on nvim 0.10.2 homebrew release. I read somewhere they are on the nightly builds only. Added them manually to my config.
Could you also help me understand the difference between quickfix and location list? Looks like location list could work together with quickfix list, since according to documentation it should be local for a window, but I am unable to build my workflow for it. Like, for example, put diagnostics from all project to the quickfix list, but put diagnostics for the current buffer to location list?
Yep, basically. FWIW it's just a list of file locations (with row and col) that an LSP server gives you when you ask it "where do i use 'thing' under my cursor, which is at filr X, line Y, col Z". It's mostly used for variables, functions and structs/classes, yes
What I want to know is, how can you easily delete an item from the quickfix list?? My brain wants to `dd` over entries like in oil.nvim or mini.files, but alas the quickfix is an immutable buffer. Do I need a plugin for this or is there a way I could remap this???
If you have lsp installed and it supports you can go to function definition, declaration, implementation or usage. You can navigate the jump-list (places where your cursor was) using CTRL+o to move back and CTRL+i to go forward. The jumplist can be used with the quickfix feature, for example to quickly go to a line of code containing errors.
lol I was seardhing for the quick fix. But i was thinking quickfix differently. Wanted to know if there is some way to automatically import the missing variables in javascript.
I think if you leave out the global 'g' flag with the cdo substitute it should only replace all the correct references, since we got the references from the lsp. 😊 Edit: I was wrong :D
the keymap was really great. The only thing it didn't work for me was the ":.lua" command to execute the line. I gonna check the documentation, it seems pretty neat.
Aren't you tired of writing code exclusively using a keyboard? Pressing the 'ESC' key or typing 'jj' non-stop for several hours is really exhausting. By the end of the day, I'm genuinely tired of writing code.
TJ raising a new generation of vim enjoyers. Thanks for all the effort, it's much appreciated.
C stands for quiCk.
Because q was taken for reQord or maQro
@@IainSimmons Me trying to quit: _recording @q_
"obviously"... ;)
quiC fiC
The plugins ‘quicker’ and ‘bqf’ make the quickfix list pure magic.
Also pqf is nice alongside them
Not to forget Trouble from folke. Very nice quickfix integration.
I'm really enjoying this series TJ. I'm following along with my own config, building it up as we go, and it's been extremely useful. Thank you!
For the diagnostics quickfix, I have ":Telescope diagnostics bufnr=0" (and one without bufnr) mapped. This makes it super easy to filter diagnostics as needed and then Ctrl+Q to send the results to the quickfix list.
finally he finds his way , go to vim event , and show his expertises to world, thanks , your tongue is awesome for this purpose
Quick fix list with telescope is dope
Great video, I use :cdo a lot to refactoring, thanks TJ, I'm always learning something new in Neovim with you!!
Grok the pain away. I feel half as lost as I was at the begining of this series
TJ, Thanks for making videos like these.
Thank you so much this video was extremely helpful
One of my early keybinds that i love. Up down opens and closes quick fix while left right goes next previous
This is the video I never knew I needed
cwickfix
Learning NeoVim while learning C doing Advent Of Code. Good for me that you're doing an Advent of Neovim ! For now I'm mostly using it like I used Vim, I haven't configured an LSP or I have one and I don't know how to use the autocomplete and stuff, but anyway it's really fun and interesting. Will keep at it for at least 3 months and I'll see if I ditch VS Code for good (although I never had anything against it beside some slowing up sometimes on personal projects).
Thank you for the work !
Love this series!
This is great, thanks!
Can you also do a video about arg and arglist?
yet another cool feature of quickfix list is that you can move through the history with colder/cnewer commands
I have been using vim for 4 years and didn't know about this damn.
Quickfix is goat and one of many reasons I won't switch over to zed; which is probably the most interesting alternative out there right now.
Some of these mappings (like grr) and other LSP ones were not default on nvim 0.10.2 homebrew release. I read somewhere they are on the nightly builds only. Added them manually to my config.
Could you share it? that'd be awesome
Could you also help me understand the difference between quickfix and location list? Looks like location list could work together with quickfix list, since according to documentation it should be local for a window, but I am unable to build my workflow for it. Like, for example, put diagnostics from all project to the quickfix list, but put diagnostics for the current buffer to location list?
is there a way to pipe all marks in a buffer to the quickfix list, in a large codebase, that would be very helpful for me
i can use :lua=vim.api.nvim_buf_get_mark(0, 'a') to get individual marks but how do i get an array for the entire page
Just dropped into this video series… what is a reference? Is that all of the other places in the module/file/project that a variable is “referenced”?
Yep, basically. FWIW it's just a list of file locations (with row and col) that an LSP server gives you when you ask it "where do i use 'thing' under my cursor, which is at filr X, line Y, col Z". It's mostly used for variables, functions and structs/classes, yes
What I want to know is, how can you easily delete an item from the quickfix list?? My brain wants to `dd` over entries like in oil.nvim or mini.files, but alas the quickfix is an immutable buffer. Do I need a plugin for this or is there a way I could remap this???
quickfix reflection
how does he do Ctrl + an arrow to jump words in the command mode?
would love to see video for location list , as they are still confusing to me for some reason.
Can you get to "jump to function" and "jump back"????
If you have lsp installed and it supports you can go to function definition, declaration, implementation or usage. You can navigate the jump-list (places where your cursor was) using CTRL+o to move back and CTRL+i to go forward. The jumplist can be used with the quickfix feature, for example to quickly go to a line of code containing errors.
lol I was seardhing for the quick fix. But i was thinking quickfix differently.
Wanted to know if there is some way to automatically import the missing variables in javascript.
Those are called "code actions". It's sad VSCode don't use the proper names for things (worse if you think that they made up the names).
Is it me, or is volume very low?
I think C is for "change".
Like cdo is "change do" and cfdo is "change file do"
This is great 🤯
cuickfix
Wonderful :)
I think if you leave out the global 'g' flag with the cdo substitute it should only replace all the correct references, since we got the references from the lsp. 😊
Edit: I was wrong :D
Only because the references were the firsts in each line, it's not reliable.
You are right. Thanks for the correction.
I always thought c was for current. LOL
Let's go
C for quickfix is far better than K for knife
More like a slowfix for me
cuiqfix
if you write "cuick" and pronounce it in spanish, it sounds exactly like "quick", so maybe that's why
Cuikfix
the keymap was really great. The only thing it didn't work for me was the ":.lua" command to execute the line. I gonna check the documentation, it seems pretty neat.
I was having trouble with that one too, I kept getting errors even in nvim 0.10.x
@@Bvngee E471: Argument required ?
btw, I had 0.9.5 and upgraded to 0.10.2 and it worked.
@@caioleonhardt yup, that was the one. I’ll keep that in mind thanks
Why the amused reaction to "c"? It's spelled "cuic" (not "quick") after all. 🤓
Aren't you tired of writing code exclusively using a keyboard? Pressing the 'ESC' key or typing 'jj' non-stop for several hours is really exhausting. By the end of the day, I'm genuinely tired of writing code.
this is g@eat! thank you!