HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
elsamuko
fsrc
C2019–2019
elsamuko / fsrc

fsrc

Fast code search

Developer Tools
Explore on GitHubRead Hacker News discussions
2Distinct people
4Mentions
0Explicit recommenders
8GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fast code search

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour4 dated mentions

Observed mentions: 2019-07-05 17:31:38 UTC to 2019-07-06 16:11:23 UTC.

0122019-07-05 17:00:00 UTC to 2019-07-05 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJul 5, 17:002019-07-05 18:00:00 UTC to 2019-07-05 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-05 19:00:00 UTC to 2019-07-05 20:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-07-05 20:00:00 UTC to 2019-07-05 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-05 21:00:00 UTC to 2019-07-05 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-05 22:00:00 UTC to 2019-07-05 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-05 23:00:00 UTC to 2019-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 00:00:00 UTC to 2019-07-06 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 01:00:00 UTC to 2019-07-06 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 02:00:00 UTC to 2019-07-06 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 03:00:00 UTC to 2019-07-06 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 04:00:00 UTC to 2019-07-06 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 6, 04:002019-07-06 05:00:00 UTC to 2019-07-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 06:00:00 UTC to 2019-07-06 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 07:00:00 UTC to 2019-07-06 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 08:00:00 UTC to 2019-07-06 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 09:00:00 UTC to 2019-07-06 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 10:00:00 UTC to 2019-07-06 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 11:00:00 UTC to 2019-07-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 12:00:00 UTC to 2019-07-06 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 13:00:00 UTC to 2019-07-06 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 14:00:00 UTC to 2019-07-06 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 15:00:00 UTC to 2019-07-06 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-06 16:00:00 UTC to 2019-07-06 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 6, 16:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 5, 17:002019-07-05 17:00:00 UTC2019-07-05 18:00:00 UTC202
Jul 5, 18:002019-07-05 18:00:00 UTC2019-07-05 19:00:00 UTC000
Jul 5, 19:002019-07-05 19:00:00 UTC2019-07-05 20:00:00 UTC101
Jul 5, 20:002019-07-05 20:00:00 UTC2019-07-05 21:00:00 UTC000
Jul 5, 21:002019-07-05 21:00:00 UTC2019-07-05 22:00:00 UTC000
Jul 5, 22:002019-07-05 22:00:00 UTC2019-07-05 23:00:00 UTC000
Jul 5, 23:002019-07-05 23:00:00 UTC2019-07-06 00:00:00 UTC000
Jul 6, 00:002019-07-06 00:00:00 UTC2019-07-06 01:00:00 UTC000
Jul 6, 01:002019-07-06 01:00:00 UTC2019-07-06 02:00:00 UTC000
Jul 6, 02:002019-07-06 02:00:00 UTC2019-07-06 03:00:00 UTC000
Jul 6, 03:002019-07-06 03:00:00 UTC2019-07-06 04:00:00 UTC000
Jul 6, 04:002019-07-06 04:00:00 UTC2019-07-06 05:00:00 UTC000
Jul 6, 05:002019-07-06 05:00:00 UTC2019-07-06 06:00:00 UTC000
Jul 6, 06:002019-07-06 06:00:00 UTC2019-07-06 07:00:00 UTC000
Jul 6, 07:002019-07-06 07:00:00 UTC2019-07-06 08:00:00 UTC000
Jul 6, 08:002019-07-06 08:00:00 UTC2019-07-06 09:00:00 UTC000
Jul 6, 09:002019-07-06 09:00:00 UTC2019-07-06 10:00:00 UTC000
Jul 6, 10:002019-07-06 10:00:00 UTC2019-07-06 11:00:00 UTC000
Jul 6, 11:002019-07-06 11:00:00 UTC2019-07-06 12:00:00 UTC000
Jul 6, 12:002019-07-06 12:00:00 UTC2019-07-06 13:00:00 UTC000
Jul 6, 13:002019-07-06 13:00:00 UTC2019-07-06 14:00:00 UTC000
Jul 6, 14:002019-07-06 14:00:00 UTC2019-07-06 15:00:00 UTC000
Jul 6, 15:002019-07-06 15:00:00 UTC2019-07-06 16:00:00 UTC000
Jul 6, 16:002019-07-06 16:00:00 UTC2019-07-06 17:00:00 UTC101

What Hacker News says

4 sources
elsamuko·Jul 6, 2019
I included qmake and added a `deploy.sh` in the main source folder, which generates the deployed zip file. Let me know, if this doesn't build. * gitignore behaviour: If there is a .git folder in the search folder, it uses git ls-files to get all files to search in * a .git folder itself is never searched * hidden folders and files are searched * binaries are ['detected'](https://github.com/elsamuko/fsrc/blob/f1e29a3e24e5dbe87908c4ca84775116f39f8cfe/src…), if they contain two binary 0's within the first 100 bytes or are PDF or PostScript files. * pipe behaviour is not implemented yet * it supports only one option-less argument as search term * folders are set with -d
In How FZF and ripgrep improved my workflow
burntsushi·Jul 5, 2019
I don't know what Qt Creator is. Please provide tools to build your code from the command line. I did some playing around with your binary, but it's pretty hard to benchmark because I don't know what your tool is doing with respect to .gitignore, hidden files and binary files. Your output format is also non-standard and doesn't revert to a line-by-line format when piped into another tool, so it's exceptionally difficult to determine whether the match counts are correct. Either way, I don't see any evidence that fsrc is faster. That you're using a fast SIMD algorithm is somewhat irrelevant; ripgrep uses SIMD too. On my copy of the Linux checkout (note the `-u` flags passed to ripgrep): $ time /tmp/fsrc PM_RESUME | wc -l 41 real 0.143 user 0.330 sys 0.474 maxmem 67 MB faults 0 $ time rg -uuu PM_
Read the rest
RESUME | wc -l 17 real 0.149 user 0.564 sys 0.690 maxmem 13 MB faults 0 $ time rg -uu PM_RESUME | wc -l 17 real 0.112 user 0.481 sys 0.675 maxmem 13 MB faults 0 $ time rg -u PM_RESUME | wc -l 17 real 0.118 user 0.507 sys 0.701 maxmem 13 MB faults 0 $ time rg PM_RESUME | wc -l 17 real 0.142 user 0.749 sys 0.726 maxmem 21 MB faults 0 I originally tried to run `fsrc` on a single file (in order to better control the benchmark), but I got an error: $ time /tmp/fsrc 'Sherlock Holmes' /data/benchsuite/subtitles/2018/OpenSubtitles2018.raw.sample.en Error : option '--term' cannot be specified more than once Usage : fsrc [options] term Options: -h [ --help ] Help -d [ --dir ] arg Search folder -i [ --ignore-case ] Case insensitive search -r [ --regex ] Regex search (slower) --no-git Disable search with 'git ls-files' --no-colors Disable colorized output -q [ --quiet ] only print status Build : v0.9 from Jul 5 2019 Web : https://github.com/elsamuko/fsrc real 0.005 user 0.002 sys 0.002 maxmem 9 MB faults 0
In How FZF and ripgrep improved my workflow
elsamuko·Jul 5, 2019
I'm currently working on a searcher on my own: https://github.com/elsamuko/fsrc When I started, I didn't know ripgrep, now I use it as reference. Of course it's still slower for regex searches and it has less options, but in some cases (e.g. simple string matching search), it is faster than rg (PM_RESUME in 160-170ms), mostly thanks to mischasan's fast strstr: https://mischasan.wordpress.com/2011/07/16/convergence-sse2-... If you want, let me know, what you think about it.
In How FZF and ripgrep improved my workflow

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.