Login

Recent searches

No recent searches

Search options

Only available when logged in.
fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

fosstodon.org: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

Public *
Bobulous :rust: :codeberg:

I created a crib sheet for the text editor:

bobulous.org.uk/coding/Helix-c

Best viewed on a big screen.

As usual I intended the new page to be compact and concise; and as usual it ended up being huge and rambling. Hopefully it'll still be of use to people who aren't fully familiar with the most useful keys and commands. (And just maybe of vague interest to users who are thinking about trying Helix.)

Let me know if you spot anything incorrect.

www.bobulous.org.ukHelix crib sheetA quick reference for the key bindings and modes used in the multi-modal text editor Helix.
#HelixEditor#FOSS#RustLang
Public
stateful being

@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

Public
Bobulous :rust: :codeberg:

@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.

Public
stateful being

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

Public
Bobulous :rust: :codeberg:

@unspeaker At a guess, I reckon it depends on the language.

I reckon Rust development would be painful without the rust-analyzer running in the background to warn that the borrow checker was getting angry.

Possibly other languages wouldn't need active evaluation, though.

Public *
stateful being

@bobulous

for #rust i run #bacon 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!

background code checker. Contribute to Canop/bacon development by creating an account on GitHub.
GitHubGitHub - Canop/bacon: background code checkerbackground code checker. Contribute to Canop/bacon development by creating an account on GitHub.
Bobulous :rust: :codeberg:

@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.

Mar 15, 2025, 08:56 PM·Public
0boosts·3favorites
ExploreLive feeds
About