FSearch

A search utility focusing on performance and advanced features

View the Project on GitHub cboxdoerfer/fsearch

Build Status Translation status

FSearch is a fast file search utility, inspired by Everything Search Engine. It’s written in C and based on GTK+3.

Note: The application is still in beta stage, but will see its first release as soon as localization support has been added

Features

Requirements

Download

Arch Linux (AUR)

https://aur.archlinux.org/packages/fsearch-git/

openSUSE (unoffical)

https://software.opensuse.org/download.html?project=home%3AAsterPhoenix13&package=fsearch

Ubuntu

Daily Development Builds PPA

https://launchpad.net/~christian-boxdoerfer/+archive/ubuntu/fsearch-daily

PPA Installation
sudo add-apt-repository ppa:christian-boxdoerfer/fsearch-daily
sudo apt-get update
sudo apt install fsearch-trunk

Roadmap

https://github.com/cboxdoerfer/fsearch/wiki/Roadmap

Build Instructions

https://github.com/cboxdoerfer/fsearch/wiki/Build-instructions

Localization

The localization of FSearch is managed with Weblate.

https://hosted.weblate.org/projects/fsearch/

If you want to contribute translations please submit them there, instead of opening pull requets on Github. Instructions can be found here: https://docs.weblate.org/en/latest/user/basic.html

And of course: Thank you for taking the time to translate FSearch!

Why yet another search utility?

Performance. On Windows I really like to use Everything Search Engine. It provides instant results as you type for all your files and lots of useful features (regex, filters, bookmarks, …). On Linux however I couldn’t find anything that’s even remotely as fast and powerful.

Before I started working on FSearch I took a look at all the existing solutions I found (MATE Search Tool (formerly GNOME Search Tool), Recoll, Krusader (locate based search), SpaceFM File Search, Nautilus, ANGRYsearch, Catfish, …) to find out whether it makes sense to improve those, instead of building a completely new application. But unfortunately none of those met my requirements:

Looking for a command line interface?

I highly recommend fzf or the obvious tools: find and (m)locate

Why GTK+3 and not Qt5?

I like both of them. And in fact my long term goal is to provide console, GTK+3 and Qt5 interfaces, or at least make it possible for others to build those by splitting the search and database functionality into a core library. But for the time being it’s only GTK+3 because I tend to like C more than C++ and I’m more familiar with GTK+ development.

Questions?

Email: christian.boxdoerfer[AT]posteo.de