Yo TJ. My brother was jealous that you pinned my youtube comment last video. This is a shoutout to him. Also, how do you spell the french version of JSON?
@@vaisakh_km Yeah, I'm just teasing. I was going to try to get my comment pinned to rub it in Joey's face, but when I came down here, he was already pinned again.
Next level stuff! It's really cool that you're showcasing what diagnostics can do and how easy it is to tailor sophisticated features that speed up my workflow 👍👍
The things you do - they look like magic! And then again - you make us feel like we could be magicians, too! If we only put a little more work in 😉 Thank you!!!
Where have you been all my life? Long time Vim user here, never bothered to learn vimscript, but I like lua. Recently adopted neovim and awesomewm which are both scriptable with lua, life just took a turn for the better! I was on the fence about neovim for a long time, but not anymore! Thank you for all the effort you have put into the project! If you haven't already (I'll browse through the channel), I'd like to request a similar tutorial on how to generate input for the quickfix list too.
Great video as always! It would be good if you could make a video about how to test functions that act on buffers, in Lua. Like, for example, let's say a function that gets the contents of the current line, and does some processing on it.
Hi @TJDeVries! Neovim diagnostics is a great data storage for such cases. I implemented this idea to run RSpec tests(with slight modifications). Now I enjoy working with tests more than ever. Thanks for sharing your ideas and implementation details. P.S. Repeating things while explaining a topic is actually a valuable habit. Cheers!
Yo Teej, Kudos for this implementation, it is absolutely insane. Just if you are interested, I made a few modifications in which I cover: A. Executions with package orientation. Really good to apply this GoTestOnSave user command to API development, which is my use case scenario. B. Table test Handling, in which I stack the resulting virtual text and diagnostics in the "father" or containing test Again, thank you, you have awaken my interest in Neovim plugin development. Cheers!
Starting my Programming Journey as I'm switching careers. Everyone is telling me to use vs code with all its integrated, easy to use, plugins. I'm over here trying to set up a Neo vim from scratch and implementing run, test and debugging, commands. All I know is that a mentor of mine told me to keep debugging/testing at the core, as this will help me understand better. Would like to see some comments. Should I keep diving into this rabbit hole of neovim? Or just use vscode and miss out all the fun?
That is just coooooooooooooool. I believe that nvim can do everything! I recently put all my nvim config in the container base on nixos/nix docker image. I found it quite portable to put on any server and machine with zero configuration. But when it has a great drawback that nvim in the docker cannot interact with the project environment on the host or in other docker. Can you figure out how to show this problem or any suggestions? I ask the same question to ThePrimeagen, too. LOL
I have been thinking of something like that, to list the output of these tests/and other commands inside Neovim,may be in quickfix. This video would be really helpful in my endeavour. However the difficult part would be parsing the output from stdout as i doubt all programming language would have that nice json formatting options. Now off i go to start Gooding more on that
This is different because it is using diagnostics. In my opinion, the quickfix provides a much easier alternative. In this case, you just need to set an errorformat string and makeprg (e.g. makeprg=go test ./... and errorformat+=%E%f:%l:\ %m,%-G%.%# and that's pretty much it.)
Would this be modifiable to make it so on file save I could have yarn run my build and then populate all of the errors in the quickfix window and bring it up?
Am I missing it? Would you happen to have somewhere you're hosting this file where we can give it a read without having to follow your cursor in the video?
Followed this but getting error on line 100 for add_golang_test. I don't have a full error message when I try to run it. I went by the code in the video, so its possible I missed something. I also tried to join your discord and it says its invalid now. ** EDIT ** I found your code in the repo for this, but it now errors out on line 113. I do need to learn lua better. I wanted to use this as my base while I worked through lean go with tests.
1:20 FVCK I just pronounced CIA out loud and realized I've been translating -acronyms- initialisms wrong all my life, but only in my head. Like, any -acronyms- initialisms I think up shows up in my mind as spelled in the same language as the rest of the sentence but I always spoke it out loud right. What the hell. Deciding whether to put a "like" before that sentence led me to learn the word sememe. Which is very funny in the ways it illustrates itself. Which reminds me of the word autological that cannot logically address itself. My conclusion being, I shouldn't spend the night trying to learn neovim in one sitting, there is a point of diminishing returns where I get too distracted by the fact I have internet access to actually watch a TH-cam video series to the end.
@@Mankepanke Using vim.g.mapleader = “ “ didn’t work, and I tried as well Instead of double quotes. Im wondering if it’s because I am using WSL but haven time to spin up a VM to verify
@@Zzznmop yeah, just checked my own dotfiles. Your snippet (vim.g.mapleader = " ") works for me. Strange. I don't think something like WSL should be the cause of a problem like that.
@@Mankepanke you were right. I didn’t reference my key mapping directory properly! It works now and I’m rocking a full Lua config. Thanks for considering my issue :)
Very bad video. Right out of the gate you show `./...` I've had to google that. Apparently it's terminal notation specific to Go toolchain: test, build, install, fmt (etc?) This directory notation refers to all the Go packages in all subdirectories. Maybe this video is not that bad, cause I'm having fun. But I've just wanted to know how to pipe lame flake8 to the diagnostics without lame plugins. Jokes aside, Thank you, Tj, great stuff! You are an inspiration, you are incredibly intelligent. You are much smarter than Primagen. What a clown is this Primagen? Jokes aside again, I love Prime too, but you are much smarter. 😂
Yo TJ. My brother was jealous that you pinned my youtube comment last video. This is a shoutout to him. Also, how do you spell the french version of JSON?
maybe your brother needs to think of such genius comments. then he can be pinned too.
you spell it the same. there's just only one way to say it ;)
This is the worst day of my life
JSÓN
@@moatcozza why?
are you his brother?
@@vaisakh_km Yeah, I'm just teasing. I was going to try to get my comment pinned to rub it in Joey's face, but when I came down here, he was already pinned again.
Thanks!
Next level stuff! It's really cool that you're showcasing what diagnostics can do and how easy it is to tailor sophisticated features that speed up my workflow 👍👍
Starting to move from VSCode to NeoVim to code from iPad and any other device, this is awesome, extendable editor!
The things you do - they look like magic! And then again - you make us feel like we could be magicians, too! If we only put a little more work in 😉 Thank you!!!
Where have you been all my life? Long time Vim user here, never bothered to learn vimscript, but I like lua. Recently adopted neovim and awesomewm which are both scriptable with lua, life just took a turn for the better! I was on the fence about neovim for a long time, but not anymore! Thank you for all the effort you have put into the project! If you haven't already (I'll browse through the channel), I'd like to request a similar tutorial on how to generate input for the quickfix list too.
Thanks for the amazing work on Neovim, you and all involved. Really happy with It!
Great video as always!
It would be good if you could make a video about how to test functions that act on buffers, in Lua.
Like, for example, let's say a function that gets the contents of the current line, and does some processing on it.
Hi @TJDeVries! Neovim diagnostics is a great data storage for such cases. I implemented this idea to run RSpec tests(with slight modifications). Now I enjoy working with tests more than ever.
Thanks for sharing your ideas and implementation details.
P.S. Repeating things while explaining a topic is actually a valuable habit. Cheers!
Extremely useful! Hope you keep making videos showing off what can be done with the Lua API :)
Yo Teej, Kudos for this implementation, it is absolutely insane.
Just if you are interested, I made a few modifications in which I cover:
A. Executions with package orientation. Really good to apply this GoTestOnSave user command to API development, which is my use case scenario.
B. Table test Handling, in which I stack the resulting virtual text and diagnostics in the "father" or containing test
Again, thank you, you have awaken my interest in Neovim plugin development.
Cheers!
Amazing!!!
It's just I have to say.
Thank you man!!!
Thank you!
Amazing video! Now I know what to do during the weekend.
This is some top tier content.
Really like these video [series] that you're doing, keep them coming!
This is so awesome! I need this for Lua plugin development!
Well this is just fantastic
Diagnostics look nice!!
I kinda wish I could make em show up in a popup tho
Thanks for another useful and inspiring video!
Had to smash the like button before the video starts.
Where is that clip with ThePrimeagen holding a presentation and saying "it's actually French" from?
I would also love to know
thank you, this is really inspiring,
Could you provide an example of how the find_test_line function is working?
Starting my Programming Journey as I'm switching careers. Everyone is telling me to use vs code with all its integrated, easy to use, plugins. I'm over here trying to set up a Neo vim from scratch and implementing run, test and debugging, commands. All I know is that a mentor of mine told me to keep debugging/testing at the core, as this will help me understand better. Would like to see some comments. Should I keep diving into this rabbit hole of neovim? Or just use vscode and miss out all the fun?
Thank you for doing this!
That is just coooooooooooooool. I believe that nvim can do everything! I recently put all my nvim config in the container base on nixos/nix docker image. I found it quite portable to put on any server and machine with zero configuration. But when it has a great drawback that nvim in the docker cannot interact with the project environment on the host or in other docker. Can you figure out how to show this problem or any suggestions? I ask the same question to ThePrimeagen, too. LOL
I want continiuoue of bash 2 basics videos!
Repetition is the friend of the adult learner.
diagnostics are cool
Greeeeoeatttttttt!!!!!!
Nice video
I have been thinking of something like that, to list the output of these tests/and other commands inside Neovim,may be in quickfix. This video would be really helpful in my endeavour. However the difficult part would be parsing the output from stdout as i doubt all programming language would have that nice json formatting options.
Now off i go to start Gooding more on that
This is different because it is using diagnostics. In my opinion, the quickfix provides a much easier alternative. In this case, you just need to set an errorformat string and makeprg (e.g. makeprg=go test ./... and errorformat+=%E%f:%l:\ %m,%-G%.%# and that's pretty much it.)
finally its come
Does somebody know what colorscheme tj used there?
thanks, super helpful.
Would this be modifiable to make it so on file save I could have yarn run my build and then populate all of the errors in the quickfix window and bring it up?
Am I missing it? Would you happen to have somewhere you're hosting this file where we can give it a read without having to follow your cursor in the video?
Make this a plugin 😍
Followed this but getting error on line 100 for add_golang_test. I don't have a full error message when I try to run it. I went by the code in the video, so its possible I missed something. I also tried to join your discord and it says its invalid now.
** EDIT **
I found your code in the repo for this, but it now errors out on line 113. I do need to learn lua better. I wanted to use this as my base while I worked through lean go with tests.
Just in case anyone is struggling with this problem, change the line 111 to "if test.success and test.line then"
@@tuliobrunoro4136 Thank you, this fixed an error I was having
Where is the github link?
1:20 FVCK I just pronounced CIA out loud and realized I've been translating -acronyms- initialisms wrong all my life, but only in my head. Like, any -acronyms- initialisms I think up shows up in my mind as spelled in the same language as the rest of the sentence but I always spoke it out loud right. What the hell. Deciding whether to put a "like" before that sentence led me to learn the word sememe. Which is very funny in the ways it illustrates itself. Which reminds me of the word autological that cannot logically address itself. My conclusion being, I shouldn't spend the night trying to learn neovim in one sitting, there is a point of diminishing returns where I get too distracted by the fact I have internet access to actually watch a TH-cam video series to the end.
diagnostic is as cool as TJ. LOL
This is neat but Im still too dumb to map my leader to space in lua
Isn't it just
vim.o.leader = ""
?
@@Mankepanke Using vim.g.mapleader = “ “ didn’t work, and I tried as well Instead of double quotes. Im wondering if it’s because I am using WSL but haven time to spin up a VM to verify
@@Zzznmop yeah, just checked my own dotfiles. Your snippet (vim.g.mapleader = " ") works for me.
Strange. I don't think something like WSL should be the cause of a problem like that.
@@Mankepanke you were right. I didn’t reference my key mapping directory properly! It works now and I’m rocking a full Lua config. Thanks for considering my issue :)
i'm sorry but we don't say JSON like that in french 🙂
Very bad video. Right out of the gate you show `./...`
I've had to google that.
Apparently it's terminal notation specific to Go toolchain: test, build, install, fmt (etc?)
This directory notation refers to all the Go packages in all subdirectories.
Maybe this video is not that bad, cause I'm having fun.
But I've just wanted to know how to pipe lame flake8 to the diagnostics without lame plugins.
Jokes aside,
Thank you, Tj, great stuff!
You are an inspiration, you are incredibly intelligent. You are much smarter than Primagen.
What a clown is this Primagen?
Jokes aside again,
I love Prime too, but you are much smarter.
😂
ja son .. kekw
You could also add Golang code coverage like 'rafaelsq/nvim-goc.lua'
Another classic. btw TIL vim.json.decode. When I search for help on that I get nothing, is it just me?
me too, do you have resolve this proble?