In the fuzzy finder, you can also use tab and S-tab instead of C-n & C-p. Comes easier when dealing with short lists where you just go downwards, e.g. space b.
thanks a lot for these direct videos, no PR bullshit - right from installation -- all the way to full IDE depth - no "figure yourself from here on". i needed this.
Thanks for the video. Btw with backslash you mean forward slash :P I really appreciate these edge case / advances key combinations. There are definitely some things that keep me from changing from VSCode+vim to helix. Like: is it going to work with larger C / C++ projects? Will the LSP find all includes, CMake files and show me function suggestions? And some things do feel slower compared to vim, like deleting a word is miwd in helix and diw in vim (less keystrokes)
I remember reading somewhere that Helix developers have admitted that certain actions take more keystrokes, and this is because they want to optimise for clarity (with their selection → action model) rather than fewer keystrokes.
Looks like in newer Helix versions the finder with what you call analyzer warnings (LSP diagnostics in the Helix docs) is remapped to [space] d and [space] D. [space] g is now mapped to the experimental debugger.
@@muhammadraza7231how is this a copy lol. the grammar to move along the file and make changes is significantly different and comes from a text editor called kakoune. also you don't need to configure helix to the extent that you have to neovim. setting up helix hardly requires 20 lines of config. neovim requires quiite a bit of tinkering and understanding to even get to a working lsp. i love both but they're just not the same. if they were the same all vim people would be using helix.
How different is Helix from your standard LunarVim installation? I understand that a barebone (n)vim config is quite daunting for the newer user, but is that their largest difference?
Helix is quite a bit slimmer than LunarVim, and has zero dependencies. LunarVim is good. Helix is good. They are all good. Try them out and pick the one you like.
The startup time of LunarVim is way more than Helix or just NeoVim. It is the maie reason I am not using LunarVim. NvChad on the other hand is much faster and a pretty good config.
You have to start slowly. First find some good setup. I recommend the latest Primeagen settings video. Than start by using the most simple commands. DON'T overcomplicate. At first you might need selection/insertion mode switch, copy, paste, delete, hjkl. To speed up your navigation just increase your key repeat speed or learn w, W, b, B, e. As you get used to it start using a few more other commands. You will be really slow so feel free to switch to your previous editor when needed.
I really like the idea of helix but im having alot of issues with helix on manjaro. It is very slow and unresponsive even just pressing escape in insert mode to get into normL mode can take over a second at times
7:11 > _"space > shift+g"_ (on screen:) _"G: open workspace diagnostic picker"_ the G ain't working for me, and ain't shown either after space on helix 22.05 -i wish you moved your head a bit to the side-
Literally just press space and ? For anyone wondering why there isn't a fuzzy finder he typed `hx .` There's a period for the current directory, pretty easy to miss... Your config will be empty. For `:theme` he doesn't press enter, he tabs after typing the command to pull up the list of themes.
consider googling mawww's vim golf using kakoune. there's a lot you can learn and it's close enough to helix for loads of nice practice leveraging multiple selection
also: for those who don't know, mawww's the maker of kak. while some say vim golf is impractical, it's really just giving you an opportunity to do a bunch of intentional, specific practice. after i finish one problem, i repeat it a few times, especially the parts of the solution that i'd like to make muscle memory. then i often modify the problem to make it more general or applicable to what i work on. for example, if the problem looks like this a b c then would my solution work, without any changes, if the problem had +1000 lines instead of three? i tend prefer solutions that are independent of those kinds of particularities without sacrificing too much speed. when i'm coding, i don't want to be counting movements, but instead thinking about the structure.
With lazygit you can do `sh lazygit` from helix and then just hit q when you're do to return to helix
TIL!
I tried doing that but it glitches out when I do 'q' to go back. I am using windows terminal running wsl Ubuntu.
@@maximus1172 I'm on Mac and it gives me a weird thing where I see Laygit but I'm still navigating the regular buffer
Super informative video! I've been using Helix for a few months now, and there were still a few things I learnt here. Thank you very much!
In the fuzzy finder, you can also use tab and S-tab instead of C-n & C-p. Comes easier when dealing with short lists where you just go downwards, e.g. space b.
This is dope. Concise and to the point
Your videos about Helix are the best. Thanks for telling us about this awesome editor. Keep up the good work!
Great, video!
I am waiting for part2 :)
Hey Luke, saw your commandline and for a moment thought it said my name. Loved the video, Vim geek here who will now be trying Helix.
thanks a lot for these direct videos, no PR bullshit - right from installation -- all the way to full IDE depth - no "figure yourself from here on". i needed this.
Thanks for the video.
Btw with backslash you mean forward slash :P
I really appreciate these edge case / advances key combinations.
There are definitely some things that keep me from changing from VSCode+vim to helix.
Like: is it going to work with larger C / C++ projects? Will the LSP find all includes, CMake files and show me function suggestions?
And some things do feel slower compared to vim, like deleting a word is miwd in helix and diw in vim (less keystrokes)
Yes, forward slash!
I opened up sqlite.c and clangd handled it beautifully. Never tried C++
Helix bindings are a little slower
I remember reading somewhere that Helix developers have admitted that certain actions take more keystrokes, and this is because they want to optimise for clarity (with their selection → action model) rather than fewer keystrokes.
woooow really good teaching this. i might just try this out.
Would love to see a video about setting up `lldb-vscode` if possible.
Looks like in newer Helix versions the finder with what you call analyzer warnings (LSP diagnostics in the Helix docs) is remapped to [space] d and [space] D. [space] g is now mapped to the experimental debugger.
That looks promising after vim/nvim configuring hell
9:03 lazy git - woah, what's that inside a terminal. super awesome.
cool stuff! are you going to use this editor in future?
How do u have so many themes available? I just get the default theme when I do :theme
Great content. How do I set up the lsp for python ?
I’m so glad I found this video! Exactly what I was looking for. I use Neovim every day and wanted to know whether it was worth making the switch
Definitely not it’s a copy of neovim
@@muhammadraza7231 in rust and with some different design philosophy
@@muhammadraza7231how is this a copy lol. the grammar to move along the file and make changes is significantly different and comes from a text editor called kakoune. also you don't need to configure helix to the extent that you have to neovim. setting up helix hardly requires 20 lines of config. neovim requires quiite a bit of tinkering and understanding to even get to a working lsp. i love both but they're just not the same. if they were the same all vim people would be using helix.
Is the Ctrl Z and fd a helix thing? I never seen that before, and I cannot find it on the helix docs. (Sadly it doesn't work with nushell though)
It's a shell thing.. I've used it in Linux a bit.. Ctrl-z "stops" the execution of the current program.. And fg brings it back into foreground
How different is Helix from your standard LunarVim installation? I understand that a barebone (n)vim config is quite daunting for the newer user, but is that their largest difference?
Helix is quite a bit slimmer than LunarVim, and has zero dependencies. LunarVim is good. Helix is good. They are all good. Try them out and pick the one you like.
The startup time of LunarVim is way more than Helix or just NeoVim. It is the maie reason I am not using LunarVim. NvChad on the other hand is much faster and a pretty good config.
What's your advice for someone who wants to get into modal editors like vim and helix, but finds it too intimidating?
if you have to ask this question, then you're probably not THAT interested. Just dive in if you really want to try it out
@@weirdo911aw i disagree. these editors can seem like a lot to people and they have a certain learning curve reputation. see my following comment.
hx --tutor as suggested at 0:23
or vimtutor
or 1) learn touch typing and 2) read a good book e.g. Practical Vim
You have to start slowly. First find some good setup. I recommend the latest Primeagen settings video. Than start by using the most simple commands. DON'T overcomplicate. At first you might need selection/insertion mode switch, copy, paste, delete, hjkl. To speed up your navigation just increase your key repeat speed or learn w, W, b, B, e. As you get used to it start using a few more other commands. You will be really slow so feel free to switch to your previous editor when needed.
I really like the idea of helix but im having alot of issues with helix on manjaro. It is very slow and unresponsive even just pressing escape in insert mode to get into normL mode can take over a second at times
3:13 > _"use this escape binding"_
what does those bindings do? and why is it put as a warning??
there are three ways to 'escape' in helix, this makes it one way. it's a great keybinding for beginners
Do you use helix as a daily driver?
Yes
`be` is faster than `miw`
where is the file explorer like nerdtree or nv tree ?
There isn't one. It's a bummer
Cost benefit analysis.... new keybindings for what benefit?
7:11 > _"space > shift+g"_ (on screen:) _"G: open workspace diagnostic picker"_
the G ain't working for me, and ain't shown either after space on helix 22.05
-i wish you moved your head a bit to the side-
very cool! ctrl z does nothing to me (also did not find it in the docs)
C-z / fg is a terminal feature. Here's an article www.thegeekdiary.com/understanding-the-job-control-commands-in-linux-bg-fg-and-ctrlz/
Ohh thanks
@@LukePighetti I'll have to learn the nushell or zellij equivalent!
First time paying attention to dart, at first I was about to say "How did they get JavaScript into java?"
space d/D for diagnotic on master
Just noticed that, thanks
/ is forward slash...
Yep
Arrow Keys: I am a joke to you?
Literally just press space and ?
For anyone wondering why there isn't a fuzzy finder he typed `hx .` There's a period for the current directory, pretty easy to miss...
Your config will be empty.
For `:theme` he doesn't press enter, he tabs after typing the command to pull up the list of themes.
Helix is good, make by rust but I still use vim/neovim
consider googling mawww's vim golf using kakoune. there's a lot you can learn and it's close enough to helix for loads of nice practice leveraging multiple selection
Thank you
also: for those who don't know, mawww's the maker of kak.
while some say vim golf is impractical, it's really just giving you an opportunity to do a bunch of intentional, specific practice.
after i finish one problem, i repeat it a few times, especially the parts of the solution that i'd like to make muscle memory. then i often modify the problem to make it more general or applicable to what i work on. for example, if the problem looks like this
a
b
c
then would my solution work, without any changes, if the problem had +1000 lines instead of three? i tend prefer solutions that are independent of those kinds of particularities without sacrificing too much speed. when i'm coding, i don't want to be counting movements, but instead thinking about the structure.
this is torture who comes from vscode 🥲