this post was submitted on 20 Feb 2024
31 points (63.5% liked)
Programming
17484 readers
56 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
About 6 months since I've switched away from vscode. To make Helix worth it you also need to use software that compliments it.
I work in DevOps, so I don't do a ton of programming but everything I do is via terminal. I use Kitty Terminal, ZSH with oh-my-zsh for the shell, Zellij for an emulation layer (think tiling and tab manager in kitty), nnn for in terminal file manager, and helix for editor.
I almost never leave the terminal now, except when web browsing.
I remember being really interested in Helix when it came out, but it didn't have a built-in file picker.
Is this still an issue for users? Is there a built-in solution, or a usermade solution to this?
Also, is there plugin support?
I can't use an editor without rainbow indent/brackets, without them code just takes too long to read that it becomes frustrating.
Space-f
lets you open a file in the current workspace, and:open /path
always let's you open any file on the computerPlugin support not yet I think. Not gonna lie, I chose helix over nvim for it's good out of the box experience, so I didn't actually have a need for plugins yet.
Fair enough. That would be a use case for a plugin (or simply a setting!)
Is this a file tree, or just a fuzzy finder?
Fuzzy finders aren't a substitute for a file tree picker. They're only great, until you don't know the name of a file, or until you need to know of a file's existence in the first place.
~~File tree~~ not a file tree like in a file explorer, more like the output of
find
, but with filtering. The letters you type to restrict your search only need to present in that order in the file path, not as a string.So "abc" would match "./assets/others/abort/cancel.png", not just "./assets/abc.png"
Additionally, lower case letters match case insensitive, upper case letters match case sensitive. This is surprisingly helpful if you don't use exclusively lowercase file names.