Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

File Explorer is merged to Helix editor

github.com

Post reply on HN
Print view View original

21–30 of 36 posts

Re: File Explorer is merged to Helix editor

#21

Post by homebrewer »

TacticalCoder wrote: post #20
punkbit wrote: post #16

I 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…

You're shadowbanned, mate, almost all your comments from at least the last couple of weeks are dead.

Re: File Explorer is merged to Helix editor

#22

Post by archseer »

zamalek wrote: post #12

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

https://github.com/helix-editor/helix/pull/12527

Re: File Explorer is merged to Helix editor

#23

Post by qudat »

punkbit wrote: post #16

I 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 ditched file explorer in neovim and just use fzf.

I also ditched tabs and rely on fzf on the buffers.

It’s a really powerful setup and cleans up the UI significantly

Re: File Explorer is merged to Helix editor

#24

Post by CaptainOfCoit »

homebrewer wrote: post #21
TacticalCoder wrote: post #20

Earlier quoted context omitted.

> 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…

You're shadowbanned, mate, almost all your comments from at least the last couple of weeks are dead.

Probably not the best venue, but if you read through the comments, kind of makes sense.

"Assume good faith", "Converse curiously" and "Eschew flamebait" are part of the guidelines for commenting, for good reasons.

Re: File Explorer is merged to Helix editor

#26

Post by Rehanzo »

TacticalCoder wrote: post #20
punkbit wrote: post #16

I 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…

Isn't space+f fuzzy find?

Re: File Explorer is merged to Helix editor

#27

Post by skydhash »

TacticalCoder wrote: post #20
punkbit wrote: post #16

I 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…

A file explore is great only for browsing (to get a sense of the project) and managing files (moving renaming, especially in batch). Actually opening file is better with a finder (either filename or content) and a fuzzy filter. I use emacs and consult is a great package for that (the native features mostly present a buffer with the result). A step up from VSC is acting over a result buffer and have the changes reflected back to the normal buffer. Like renaming functions when LSP can’t help you.

Re: File Explorer is merged to Helix editor

#28

Post by zamalek »

desdenova wrote: post #17
zamalek wrote: post #12

What 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 fg

PWD is does hot refer to the directory that file I am working on is in.

Re: File Explorer is merged to Helix editor

#30

Post by bryanrasmussen »

homebrewer wrote: post #21
TacticalCoder wrote: post #20

Earlier quoted context omitted.

> 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…

You're shadowbanned, mate, almost all your comments from at least the last couple of weeks are dead.

I don't think they're shadowbanned, just a lot of the comments have been banned the old-fashioned way.
Post reply on HN