Hacker News new | ask | show | jobs
by dzek69 915 days ago
This is great tool, I use it everyday, but far from it's Windows based original Everything.

Also this is anbandoned apparently, which makes me extra sad, because it lacks few crucial features like: - being able to just remove a file from the index if you delete it from the app directly (insted it shows a window how it "soon" gonna be implemented) - while i understand that indexing service is more complex job - at least caching the index would be nice, because right now when i start the app i have to wait for it to index everything again, but usually i search for files that exists for a long time, not these that was created between my fsearch uses

So yeah. Cool dead and incomplete piece of software ¯\_(ツ)_/¯ From time to time I look for better alternative, if you happen to know one - let me know.

6 comments

Hi, I'm the author of this little piece of software.

> Also this is anbandoned apparently, which makes me extra sad, because it lacks few crucial features like:

PersonalIy I wouldn't call it abandoned. I'm still working on it — not as often as I'd like to, but I'm still making progress towards the next release. Though it's still months away from being released.

> - being able to just remove a file from the index if you delete it from the app directly (insted it shows a window how it "soon" gonna be implemented)

That feature is already implemented, but there are no official builds with it yet, because other parts of the software haven't been updated after the rewrite of the database engine (e.g. loading/saving the database file is broken at the moment). Once the old feature set is working again, I'll publish the first official dev builds of the 0.3 release.

> while i understand that indexing service is more complex job - at least caching the index would be nice, because right now when i start the app i have to wait for it to index everything again, but usually i search for files that exists for a long time, not these that was created between my fsearch uses

This is already supported and part of the stable releases. The index is cached and loaded upon application start, so you can search right away, even while the new index is being built. You can also disable auto index updates when the application is launched, if you prefer manual or scheduled index update instead. Or do you mean something else?

What's the best way to help you with this project?
Most definitely code and documentation contributions and to a degree donations — although I clearly prefer the former, simply because it keeps me engaged the most by talking with others about this project, getting new ideas, etc.

But I really welcome any sort of contribution. For example there's also things like improving the main interface language (English isn't my first language, so there's likely room for improvement there), helping with support questions and bug reports, artwork, ...

Last commit 2 weeks ago? Doesn't look dead. Perhaps not actively developed by original author but seems they're still acting as a maintainer and willing to take PRs.
Me too - strangely, one of the reasons I stay on Windows is Everything (https://www.voidtools.com/) - it is just so useful.
I had Everything installed but didn't use it as much as expected. I've gravitated toward FileLocator Pro instead, which uses extremely fast metadata table searching instead of requiring an index (I don't use the Agent Ransack features).

Not a Linux expert, but out of curiosity did you try Recoll when you looked at other platforms? (https://www.lesbonscomptes.com/recoll/pages/index-recoll.htm...)

What is the pattern syntax you use most often?
Just regular fuzzy finding is the most common. For example, to attach a file instead of faffing around clicking in the open dialog, I type into fluent search(a frontend to everything) and it enters it in the current context i.e the open dialog.

It has a few other qualifiers, like big: huge: etc to search large files. Same way with time etc.

Rarely when you need it you prefix with regex: and you get everything you need.

It's very useful that both everything and fluent search integrate into explorer in that if you right click on the search result you get the same context menu as you would in explorer. Drag drop works, etc,. The issue with every other tool in every other OS is the lack of this feature. You basically have a virtual fully featured directory for every search result, simply cannot beat that.

Wait, I didn't know Everything can full search text ? is it like search preview in macOS ?
Sorry, I meant that you can fuzzy find the filenames, not the contents.

For the latter, explorer top right search bar can do it surprisingly. As for a tool with an index, recoll comes to mind.

You can use the "si:" prefix in Everything alpha to query Windows index.

https://www.voidtools.com/forum/viewtopic.php?f=12&t=9793

I have some use scenario (finding backlinks in a folder containing thousands of markdown files) where this method fits perfectly and returns results instantaneously (even ripgrep takes a second or two to find all the backlinks as it doesn't use an index).

Unfortunately the text snippet showing the context that you get in explorer is not easily retrievable via Windows API. I made a suggestion [1] to the author and he seems open to implement it.

[1] https://www.voidtools.com/forum/viewtopic.php?t=13739

I use astrogrep for searching file contents on windows, it's pretty fast. Not nearly as fast as everything but I guess that's the nature of searching full contents. Just restrict by file type and filter out node modules and it's fast enough
The most important thing is to sort by date modified by default. Usually, the file you want is very new.

After that I mostly just use "pic:" or "path:".

fd (fdfind on some distributions)
rg or fd?
rg if you want to find stuff in files

fd if you want to find stuff in filenames

fzf for when you want a fuzzy menu type of search on top of this.

I can't recommend fzf enough you can do some really powerful stuff with it. If you don't know it: it gives you a fuzzy search on things you pipe into it. It is powerful because it also can do things like running special commands ("preview") on the currently selected entry/line and allows for displaying the output in a separate pane.

So you could build a thing that e.g. let's you search and multiselect (enqueue) your music collection and on each entry display audio metadata using a custom script.

Or a blazingly fast PDF-content searcher that opens the PDF in the end. The possibilities are endless.

Edit: Here a short video showing my basic git log alias: https://youtu.be/9W27D8lrn-s

    gl: aliased to git log --all --pretty=oneline --pretty=format:"%Cgreen%h%Creset %s %Cred%d%Creset" --color=always | fzf --ansi --preview 'git show --pretty=medium --color=always $(echo {} | cut -d" " -f1)' | cut -d" " -f1
If you want to put this (fantastic, thank you very much for it!) command in your git toolbox, personally I did it like this:

1) create an executable script called `git-l` and put it in a place in your PATH, and make it executable 2) use `git l` to invoke it

You will avoid escaping hell and you can even expand/complicate it much more. The same extension principle works with other CLI tools like `kubectl`.

rg isn't really a file finder, it's a grepper.
rg --files