Fsearch, a fast file search utility for Unix-like systems
11–20 of 98 posts
Re: Fsearch, a fast file search utility for Unix-like systems
#12This 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…
> 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?
Re: Fsearch, a fast file search utility for Unix-like systems
#13How does this search filesystems quickly on linux?
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 systems a normal case insensitive substring search should finish almost instantly with few million files.
The next release will support file system monitoring with inotify and fanotify to keep the index updated. Although this has some drawbacks.
Re: Fsearch, a fast file search utility for Unix-like systems
#14The GitHub page recommends mlocate for a CLI version.
Re: Fsearch, a fast file search utility for Unix-like systems
#15Unix-like apparently does not include macOS here Edit: Or does it? https://ports.macports.org/port/fsearch/details/
Do you really need it on Mac? We've got mdfind
Testing out mdfind and trying to simply find a file in a specific directory (which only contains five files):
mdfind -onlyin . name-of-my-file.md
Nothing. mdfind -onlyin . -name name-of-my-file.md
Nothing. mdfind -onlyin /absolute/path/to/cwd -name name-of-my-file.md
Nothing.This is pretty reflective of my experience with the Spotlight GUI. Every search turns up something, but the file I want is almost never in the results.
Re: Fsearch, a fast file search utility for Unix-like systems
#16I was wondering what this adds over mlocate. It seems it's a GUI only / GUI first tool. The GitHub page recommends mlocate for a CLI version.
Likely the most significant benefit is the more powerful query language. For example you can also search by file modification date or size and use boolean operators. https://github.com/cboxdoerfer/fsearch/wiki/Search-syntax
Re: Fsearch, a fast file search utility for Unix-like systems
#17This 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…
Me too - strangely, one of the reasons I stay on Windows is Everything ( https://www.voidtools.com/ ) - it is just so useful.
Re: Fsearch, a fast file search utility for Unix-like systems
#18This 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…
rg or fd?
Re: Fsearch, a fast file search utility for Unix-like systems
#19Earlier quoted context omitted.
Me too - strangely, one of the reasons I stay on Windows is Everything ( https://www.voidtools.com/ ) - it is just so useful.
What is the pattern syntax you use most often?
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.
Re: Fsearch, a fast file search utility for Unix-like systems
#20How does this search filesystems quickly on linux?
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…