Live data from Hacker News

File Explorer is merged to Helix editor

github.com

31–36 of 36 posts

Re: File Explorer is merged to Helix editor

#31

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’m not seeing it? They don’t appear to be shadowbanned from my account.

Re: File Explorer is merged to Helix editor

#32
post #31

Earlier quoted context omitted.

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

I’m not seeing it? They don’t appear to be shadowbanned from my account.

Lots of completely harmless comments are dead, the few that are not were vouched for by someone (like myself if we're talking about this thread specifically). I don't really care either way, but the guy should be aware that he's writing into /dev/null

Re: File Explorer is merged to Helix editor

#34
post #31

Earlier quoted context omitted.

I’m not seeing it? They don’t appear to be shadowbanned from my account.

Lots of completely harmless comments are dead, the few that are not were vouched for by someone (like myself if we're talking about this thread specifically). I don't really care either way, but the guy should be aware that he's writing into /dev/null

dang seems to have outright banned him just over a fortnight ago. https://news.ycombinator.com/item?id=42653007

On Hacker News, banned accounts can still comment, but those comments are immediately dead until vouched.

Re: File Explorer is merged to Helix editor

#36
post #26

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…

Isn't space+f fuzzy find?

For me, space+f is a "fuzzy search", a filter to find by filename. You can omit some characters, e.g. `pack/back/conf` would show `packages/backend/config.z`.

I have muscle memory now, so I'd have to open the editor to confirm it. There is also another mode, that works a bit like grep I think? I haven't used it but seems that you can look for matches in file content.

Post reply on HN