Oil for nvim is THE best explorer i have used. Highly recommend
File Explorer is merged to Helix editor
11–20 of 36 posts
Re: File Explorer is merged to Helix editor
#12What I really want to see merged is the tokens in shell commands. dotnet is my day job, and the boilerplate (its luckily just namespace nowadays) gets repetitive and typo-prone. If I could just (approximately) `dotnet new class -o $cwd`...
Instead we have something like 3 closed PRs for this.
Re: File Explorer is merged to Helix editor
#13... but can it read emails? 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.
And a corollary to this law:
Except for programs embedded in applications that can already read mail (notably web apps)
Re: File Explorer is merged to Helix editor
#14Oil for nvim is THE best explorer i have used. Highly recommend
yazi for me!
Re: File Explorer is merged to Helix editor
#15Re: File Explorer is merged to Helix editor
#16I used to believe that a File explorer is crucial in my text editor; after using Helix for more than a year, I’ve discovered that is not required at all; space+f much faster use flow. I work with split terminal windows, where I have supporting windows to navigate the file system.
Happy to try a file explorer once again, it’ll be interesting to see how I feel a year later.
Re: File Explorer is merged to Helix editor
#17What I really want to see merged is the tokens in shell commands. dotnet is my day job, and the boilerplate (its luckily just namespace nowadays) gets repetitive and typo-prone. If I could just (approximately) `dotnet new class -o $cwd`... Instead we have something like 3 closed PRs for this.
Can't you just:
dotnet new class -o $PWD
fgRe: File Explorer is merged to Helix editor
#18Oil for nvim is THE best explorer i have used. Highly recommend
It is the best explorer for me too. It blends into the rest of the vim so much so that you don't feel the difference between manipulating text and files.
Re: File Explorer is merged to Helix editor
#19Oil for nvim is THE best explorer i have used. Highly recommend
It is the best explorer for me too. It blends into the rest of the vim so much so that you don't feel the difference between manipulating text and files.
I've been using vim/neovim for decades, and "so that you don't feel the difference between manipulating text and files" made no sense.
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!
Re: File Explorer is merged to Helix editor
#20I used to believe that a File explorer is crucial in my text editor; after using Helix for more than a year, I’ve discovered that is not required at all; space+f much faster use flow. I work with split terminal windows, where I have supporting windows to navigate the file system. Happy to try a file explorer once again, it’ll be interesting to see how I feel a year later.
> I’ve discovered that is not required at all; space+f much faster use flow.
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"