Live data from Hacker News

Fsearch, a fast file search utility for Unix-like systems

github.com

41–50 of 98 posts

Re: Fsearch, a fast file search utility for Unix-like systems

#41
post #3

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

Try this one

https://news.ycombinator.com/item?id=33816014

Re: Fsearch, a fast file search utility for Unix-like systems

#42
post #40

Earlier quoted context omitted.

+1 on the need for non-Spotlight options. Source code makes a mess of spotlight for everyday usage. I like Leap a lot for multimedia browsing with more precise search capabilities than spotlight: https://ironicsoftware.com/leap/

You can remove folders from spotlight under "Spotlight Privacy". I removed my source code folders, which vastly improved search results.

100%. That's when I discovered I needed non-spotlight search to bulk search what I just excluded from spotlight.

Re: Fsearch, a fast file search utility for Unix-like systems

#43
post #25

For anyone looking for a Mac equivalent, there's GoToFile[0]. As far as I've seen, this is the only app for Mac that doesn't just reuse Spotlight search (which I find to be terrible). I looked for exactly this type of app for years before finding it, and when I did, it didn't seem real with the old-fashioned website and zero mentions on sites like HN. But I can assure that it works great and it's maintained. I just w…

How does a program like this work? Is it indexing every file on the system and monitoring all events for updates?

Re: Fsearch, a fast file search utility for Unix-like systems

#44

Earlier quoted context omitted.

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

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

Re: Fsearch, a fast file search utility for Unix-like systems

#45

Earlier quoted context omitted.

Author here. The app works in two steps: Step one is building an index of the file system. This is simply done by walking the filesystem. The resulting index is stored in RAM and a file. On the next app start the index ia loaded from that file, which is much quicker than walking the file system. Step two is using this in RAM index for searching. This scales really well with the number or CPU cores and on modern syste…

This is simply done by walking the filesystem. This is the part I'm wondering about. Everything scans the filesystem very fast and there is no way it is just using 'stat' on every file then diving into the directories. Are you just using stat from C to walk the filesystem or are you doing something else? I've used sqlite to cache filesystem results and it is also extremely fast once everything is in there, but I thin…

Yes, it's simply using stat on every file/folder. There's probably some room of improvement there with clever parallelization, but it'll remain a bottleneck.

Everything is parsing a file called the MFT to build its index. This much more efficient but unfortunately this file only present on NTFS volumes, which makes it super useful on Windows systems, but not so much everywhere else.

Another benefit you get on Windows is the USN journal, which allows Everything to keep the index updated much more efficiently.

Re: Fsearch, a fast file search utility for Unix-like systems

#46
post #20

Earlier quoted context omitted.

Author here. The app works in two steps: Step one is building an index of the file system. This is simply done by walking the filesystem. The resulting index is stored in RAM and a file. On the next app start the index ia loaded from that file, which is much quicker than walking the file system. Step two is using this in RAM index for searching. This scales really well with the number or CPU cores and on modern syste…

I've never used fsearch, but I use a CLI tool that replaces locate ( https://plocate.sesse.net/ ). Do you have an idea of how the performance and index format compares with fsearch?

I'm not familiar with the internals of plocate, but I'll have a brief look at it.

Re: Fsearch, a fast file search utility for Unix-like systems

#47
post #27

Earlier quoted context omitted.

Author here. The app works in two steps: Step one is building an index of the file system. This is simply done by walking the filesystem. The resulting index is stored in RAM and a file. On the next app start the index ia loaded from that file, which is much quicker than walking the file system. Step two is using this in RAM index for searching. This scales really well with the number or CPU cores and on modern syste…

Is it possible to use eBPF for this task instead of inotify?

Maybe, but I'm not sure if there's much benefit to that. The most inefficient part of the inotify or fanotify solution is that you have to walk the file system before monitoring can even start, because you first need to know which folders and files are there to begin with. And unfortunately this can't be avoided with eBPF.

Re: Fsearch, a fast file search utility for Unix-like systems

#48
post #25

For anyone looking for a Mac equivalent, there's GoToFile[0]. As far as I've seen, this is the only app for Mac that doesn't just reuse Spotlight search (which I find to be terrible). I looked for exactly this type of app for years before finding it, and when I did, it didn't seem real with the old-fashioned website and zero mentions on sites like HN. But I can assure that it works great and it's maintained. I just w…

How does a program like this work? Is it indexing every file on the system and monitoring all events for updates?

[deleted]

Re: Fsearch, a fast file search utility for Unix-like systems

#49
post #25

For anyone looking for a Mac equivalent, there's GoToFile[0]. As far as I've seen, this is the only app for Mac that doesn't just reuse Spotlight search (which I find to be terrible). I looked for exactly this type of app for years before finding it, and when I did, it didn't seem real with the old-fashioned website and zero mentions on sites like HN. But I can assure that it works great and it's maintained. I just w…

[deleted]

Re: Fsearch, a fast file search utility for Unix-like systems

#50

Earlier quoted context omitted.

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

Post reply on HN