this post was submitted on 20 Feb 2024
31 points (63.5% liked)

Programming

17398 readers
93 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
 

Pulsar (former Atom) is still the best code editor in my opinion. It is easiest and fastest to use, has all the nice productivity boosting plugins and is overall great for all the same reasons the Atom was great. πŸš€

See also !pulsaredit@lemmy.ml

you are viewing a single comment's thread
view the rest of the comments
[–] Turun@feddit.de 1 points 8 months ago (1 children)

Space-f lets you open a file in the current workspace, and :open /path always let's you open any file on the computer

Plugin 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!)

[–] spartanatreyu@programming.dev 1 points 8 months ago (1 children)

Space-f lets you open a file in the current workspace, and :open /path always let’s you open any file on the computer

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.

[–] Turun@feddit.de 1 points 8 months ago* (last edited 8 months ago)

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