Happy to try a file explorer once again, it’ll be interesting to see how I feel a year later.
I also ditched tabs and rely on fzf on the buffers.
It’s a really powerful setup and cleans up the UI significantly
Some use "fuzzy find" on the filename, which is ultra fast too.
I use something even faster IMO: typically I know at least some of the text of the source / test code file I want to go to. So I either use a function of the editor that can "find usage" or... I simply use ripgrep, integrated in my editor, and start typing text I know is in the file I want to visit.
I still use, sometimes, a "file explorer" to find the file to open but it's not the most common.
In a way using a file explorer is "sort": things are arranged in folders/directories. Fuzzy search or finding usages or ripgrep is "search". So, basically:
"search, don't sort"
I've been editing like that since the 1990s because that's how Emacs and XEmacs do it (M-x dired command). The ease and speed of just pressing RETURN on the .. menu to go up or on the folder name to open and look inside is unrivalled and much faster than using my mouse (and better for health - avoids RSI).
Would be cool for Helix to get Emacs-like directories-as-edit-buffers functionality!
It uses a buffer/pop to navigate and edit files like you're inside a buffer
Then I watched a video from the README (https://github.com/stevearc/oil.nvim) and yup, that looks amazing and makes so much sense. Thanks GP for mentioning it!
Instead we have something like 3 closed PRs for this.
Anyway I hope this will be soon included in release! (Even if current <space>+f is also pretty good.)
That said, I wish asciinema can also show the key strokes a an annotation with the ability for the viewer to pause on each keyboard interaction.
Jamie Zawinski's Law: Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
Except for programs embedded in applications that can already read mail (notably web apps)
