Jake, thank you very much. This is the first video on vim, that convinceed me to go for it. Simple, to the point, whichnevery newbee needs to get started. Again, than you.
I've been having a blast in Neovim over the last few weeks but still working to improve my productivity. If you have questions or requests for future Neovim videos, let me know!
Hey Mateusz, thanks for watching I'm glad you liked it! Great tip I'll make sure to update my dotfiles :) EDIT: Finally got around to updating. Thanks again!
I've actually got more annoying issue. I'm following your Practical Guide and am trying to install lightline. I made the lightline.lua file which contains the single line: vim.g.lightline = {} However, now when I try to open either nvim's config init file, lightline.lua, or even init.lua, I get the following error: Error detected while processing function lightline#update[4]..lightline#init: line 4: E715: Dictionary required Do you know how to resolve this? The plugin doesn't work :( Edit: Second question: Where can I find the instructions for installing the main Python LSP for neovim? Third question: What do I install to get a debugger for Python? 4: what plugin do you use for file tree directory?
Hmmm that is an interesting error. You followed the installation steps to a T? - declare the plugin in your init.vim - source init.vim - run :PlugInstall inside init.vim - create the lightline.lua file - import the lightline.lua file within your init.lua and source it - import your init.lua within your init.vim and source it It might be helpful to skip the lua steps and configure lightline within your init.vim file first to see if that works. If it does, then you at least know where to start looking for potential config mistakes. You can do this by removing the lightline.lua import in your init.lua and adding the following to your init.vim: let g:lightline = {} An example can be found here -> github.com/itchyny/lightline.vim#colorscheme-configuration As for Python, you can find instructions for setting up pyright here -> github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#pyright
Hi, thanks for the video but what's the main benefit of vim ? I don't understand why people spent so much time to configure a tool just to be equal to a modern ide like vscode for example ? I see a lot and a lot of videos on vim so I think it must be beneficial to use it but I'm not able to grasp it. Someone can explain it to me ?
Hey! I would liken it to someone who builds their own PC vs. someone who purchases one from the store. It's not so much that the tool is superior, although there are many who will make the argument that it is, but some people just like to dive deep and tinker. I am very much in that camp. That being said, VSCode is a wonderful editor and I'm not as productive in neovim - yet. But maybe one day. Once you use Vim for a while, even just the vim emulator in VSCode, you can see why it has such a cult following. Very fun to edit text in that way, and very fast too. "Coding at the speed of thought".
"to be equal" ^^. Nah, its far beyond. Because you are using brain instead of mouse/scroll/working with code in usual boring way. Actually I don't think that vim is better:) but its different and makes coding routine fun
Hey man, nice video! In reference to 14:21, I noticed if I use: colorscheme gruvbox-material set background=dark set termguicolors The color scheme gets bugged, in that its just grey and black -- do you get this? In the video you wrote these 3 lines in the video but never compiled with :q & :so %. When I delete 'set termguicolors' the issue goes away :/ Keen to see your next vids!
Hey there! Glad you got some use out of it :) When you add the three settings above and then source the file, are you getting any error output? If not, I would make sure you have at least checked off some low hanging fruit: - You declared 'sainnhe/gruvbox-material' in your list of plugins - You ran :PlugInstall to actually install the colorscheme - You are adding the three settings below your plugin declarations After you confirm these two things, make sure to source the file using `:w` and then `:so %`. If this still gives you issues then it might have something to do with your terminal. What terminal are you using? EDIT: And thank you for watching! There's a few more that I published after this one, including the dotfiles video :) keep me posted on your colorscheme issue. It's probably a small thing you are missing to get everything rendering correctly.
One thing you might want to try is looking up your terminal's $TERM value: echo $TERM it seems you might have the same issue outlined in lightline.vim's Introduction section: github.com/itchyny/lightline.vim#introduction There's a portion of the docs that references updating your $TERM value in your shell's configuration. I know I've had issues with this in the past using Alacritty ( a terminal ). But I no longer use it. Instead I use Kitty terminal on MacOS and Windows Terminal in WSL.
I do have plans to use it yes. I'd like to dig in a little more and understand what I can do with it. Maybe the best way to get my feet wet is convert init.vim to init.lua.
Your 100th Subscriber
@MrFambo I will frame this comment to my office wall now :D
@@jakewies Even I subbed when this video came out but forgot to check which number, thought must be a big youtuber xD
@@roguegenesis7020 Glad to have you!
Thank you Jake!!! Great Video :)
Jake, thank you very much. This is the first video on vim, that convinceed me to go for it. Simple, to the point, whichnevery newbee needs to get started. Again, than you.
This comment made my day :D I'm so glad you found it useful. I'm very new to vim as well BUT it is fun to dive in and make a mess lol
I've been having a blast in Neovim over the last few weeks but still working to improve my productivity. If you have questions or requests for future Neovim videos, let me know!
That was a great video. Keep it going
I needed this! Easily explained and was exactly what I needed. Thank you!
Keep it, brother. Yeah, make videos on neovim.
Will do!
Thank you, Bro! you are amazing!!!
Not a problem! Thanks for the kind words :D
your video helps a lot, thank you
No problem! Love your name btw lol
Huh. Surprised youtube recommended me your channel. Excellent video, would’ve never guessed its from such a small channel
Glad you enjoyed Julian :) Thank you for the kind words.
Great content :)
Very nice and very well explained
Liked, Subscribed. This video is quit newbie friendly.
Hey good to have you here!
Nice nice!!
450th subscriber 😎😎
I have an alias for sourcing and editing my .zshrc config (zs and zc respectively.)
great idea. I have one for my init.vim but don't find myself in my .zshrc often enough to warrant one...yet :)
Thank you
great videos 👍😊
Thanks Panji!
Does NeoVim startup with input mode as the default?
Thanks!
Great video! Btw syntax on is now unnecessary in new nvim. It turned on as default.
Hey Mateusz, thanks for watching I'm glad you liked it! Great tip I'll make sure to update my dotfiles :)
EDIT: Finally got around to updating. Thanks again!
For aliases it's better to use .zsh_aliases file like with .bashrc and .bash_aliases
I've actually got more annoying issue. I'm following your Practical Guide and am trying to install lightline. I made the lightline.lua file which contains the single line: vim.g.lightline = {}
However, now when I try to open either nvim's config init file, lightline.lua, or even init.lua, I get the following error:
Error detected while processing function lightline#update[4]..lightline#init:
line 4:
E715: Dictionary required
Do you know how to resolve this? The plugin doesn't work :(
Edit: Second question: Where can I find the instructions for installing the main Python LSP for neovim?
Third question: What do I install to get a debugger for Python?
4: what plugin do you use for file tree directory?
Hmmm that is an interesting error. You followed the installation steps to a T?
- declare the plugin in your init.vim
- source init.vim
- run :PlugInstall inside init.vim
- create the lightline.lua file
- import the lightline.lua file within your init.lua and source it
- import your init.lua within your init.vim and source it
It might be helpful to skip the lua steps and configure lightline within your init.vim file first to see if that works. If it does, then you at least know where to start looking for potential config mistakes. You can do this by removing the lightline.lua import in your init.lua and adding the following to your init.vim:
let g:lightline = {}
An example can be found here -> github.com/itchyny/lightline.vim#colorscheme-configuration
As for Python, you can find instructions for setting up pyright here -> github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#pyright
Hi, thanks for the video but what's the main benefit of vim ? I don't understand why people spent so much time to configure a tool just to be equal to a modern ide like vscode for example ? I see a lot and a lot of videos on vim so I think it must be beneficial to use it but I'm not able to grasp it. Someone can explain it to me ?
Hey! I would liken it to someone who builds their own PC vs. someone who purchases one from the store. It's not so much that the tool is superior, although there are many who will make the argument that it is, but some people just like to dive deep and tinker. I am very much in that camp. That being said, VSCode is a wonderful editor and I'm not as productive in neovim - yet. But maybe one day. Once you use Vim for a while, even just the vim emulator in VSCode, you can see why it has such a cult following. Very fun to edit text in that way, and very fast too. "Coding at the speed of thought".
"to be equal" ^^. Nah, its far beyond. Because you are using brain instead of mouse/scroll/working with code in usual boring way. Actually I don't think that vim is better:) but its different and makes coding routine fun
it basically can be used anywhere
Hey man, nice video! In reference to 14:21, I noticed if I use:
colorscheme gruvbox-material
set background=dark
set termguicolors
The color scheme gets bugged, in that its just grey and black -- do you get this? In the video you wrote these 3 lines in the video but never compiled with :q & :so %. When I delete 'set termguicolors' the issue goes away :/
Keen to see your next vids!
Hey there! Glad you got some use out of it :)
When you add the three settings above and then source the file, are you getting any error output? If not, I would make sure you have at least checked off some low hanging fruit:
- You declared 'sainnhe/gruvbox-material' in your list of plugins
- You ran :PlugInstall to actually install the colorscheme
- You are adding the three settings below your plugin declarations
After you confirm these two things, make sure to source the file using `:w` and then `:so %`. If this still gives you issues then it might have something to do with your terminal. What terminal are you using?
EDIT: And thank you for watching! There's a few more that I published after this one, including the dotfiles video :) keep me posted on your colorscheme issue. It's probably a small thing you are missing to get everything rendering correctly.
One thing you might want to try is looking up your terminal's $TERM value:
echo $TERM
it seems you might have the same issue outlined in lightline.vim's Introduction section:
github.com/itchyny/lightline.vim#introduction
There's a portion of the docs that references updating your $TERM value in your shell's configuration. I know I've had issues with this in the past using Alacritty ( a terminal ). But I no longer use it. Instead I use Kitty terminal on MacOS and Windows Terminal in WSL.
do you have plan to use lua?
I do have plans to use it yes. I'd like to dig in a little more and understand what I can do with it. Maybe the best way to get my feet wet is convert init.vim to init.lua.
@@jakewies can't wait for the videos! you give a great explanation
@@wijaksanapanji Thank you for the kind words I appreciate it :) next one coming soon!
Is that Brad's (Traversy) voice or am I hearing things
I haven't watched a Traversy Media vid in a while but went to check out a recent one after reading this comment. I can hear it lol
Please don't use arrow keys 😣 Another bunch of useful settings for beginners would be to disable them entirely.