Back

@bobulous damn this is pretty cool. i've been looking into migrating off neovim after seeing how much stuff is going on with the tons of plugins i use and now it's easier for me to try #helix! thanks! <3

@unspeaker Yeah, I've not tried Neovim, but I keep reading about how much work is required in terms of custom configuration and plugins in order to get it ready for software development.

Helix does seem to be ready to go, so long as the required LSP is installed for your chosen language(s). The only things I've added to my config file are custom rulers, soft-wrapping enabled, and my preferred theme name.

@bobulous think i can get by with some tree-sitters + a simpler autocomplete than a whole-ass language server?

@bobulous i have no use for advanced ide functionality and lowkey hate the lsp after i tried to wrap an existing one and it turned out it's about as much of a "protocol" as defi crypto "protocols" are actual protocols...

@bobulous

for #rust i run #bacon https://github.com/Canop/bacon in a #tmux split, used to have inline checking in my #neovim with #ale but it was updating too slowly so i nixed it (or it fell off along the way? i don't remember... plugins, man...)

most worried about #typescript really - that's the one they've really got locked down. but now that i've got a cheat sheet, i'll give it a spin and see for myself!

@unspeaker In Helix rust-analyzer works nicely for me, though I did find that building large projects (e.g. the massive Servo project) would cause rust-analyzer to go so crazy that it would actually crash Helix.

Eventually learned that if you tell the cargo build command to use only about 3/4 of CPU cores, this crash does not happen. So I guess it was getting greedy and locking up the CPU wholesale, causing rust-analyzer and Helix to fall over dead.

With that fixed, it's been fine since.

@tshepang Yeah, and I keep forgetting the key combo which lets you rotate text back and forth through selected positions: Alt+( and Alt+). Not something you need very often, but saves a lot of time and effort when you do realise a use for it.

@bobulous Also why did you separate the `[´ and `]´ section? Wouldn't it be simpler to have a simple section?

@bobulous Anyway, that's a good cheat sheet, thanks for sharing

@robinm Were you looking at the page on a mobile/small screen by any chance? I realise now that without fancy nested borders (that only fit on a bigger screen) it wasn't clear that the "LSP actions" sections are part of the "Space menu" and "Goto menu" sections. So it wasn't clear, for example, that you already have to be in the Space menu in order to hit 'c' to comment the selected lines.

I've clarified the "LSP actions" headings to hopefully make it clearer that they belong to specific menus.

@robinm As for the '[' and ']' menus, I did think about merging them into one combined section, but then it becomes necessary to write an explanation of which menu does first/previous and which does last/next within the text for each key.

I aimed to have the text as compact as possible for each key (though in some cases it still ended up quite wordy) so I settled on giving each menu its own section on the page.