mozsearch
cs
mozsearch | cs | |
---|---|---|
17 | 9 | |
234 | 502 | |
0.9% | - | |
8.9 | 7.5 | |
2 days ago | 3 months ago | |
Rust | Go | |
Mozilla Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mozsearch
-
Firefox tooltip bug fixed after 22 years
- code browsing is primitive compared to https://searchfox.org/ (but most code browsing tool are, in comparison)
- my notifications are completely flooded by lots of useless information on GitHub, but that might be fixable
- our CI system (treeherder/taskcluster) scales, works on Linux/Mac/windows/Android and a bunch of version and arch, integrated with all of the other tools mentioned. Things such as auto-running tests based on the content of the patch, automatic categorization and prioritization of intermittent test failures, or auto-recording test failures and offering a pernosco recording showing the issue are just some of the features that we use daily without even thinking
-
Why SQLite Does Not Use Git
All the time. I would say at least 50% of my code browsing is done from my phone. I make heavily use of the mobile GitHub web interface for this (find-references support has been a godsend, search is still meh, I hate how they keep breaking basic find-in-page with SPA jank). Also Searchfox [0] when I need to comb through Firefox code (fast, excellent, no complaints).
Context: grad student, programming languages and systems research plus a bunch of IoT hacking on my own time. Either elder Gen Z or youngest possible Millennial, depending where you put the cutoff.
[0] https://searchfox.org
-
Sourcegraph is no longer Open Source
[4] is not really a usable 'product'. Livegrep (https://github.com/livegrep/livegrep) was inspired by it and is very usable.
[3] used to be a Google open source project as well, but it fell out of maintenance, and Sourcegraph took it over. It powers most of the basic regex/literal search in Sourcegraph.
Mozilla's code is searchable in Searchfox (https://searchfox.org/) which uses the indexer from Livegrep, combined with their own Git indexer and language-specific cross reference databases.
OpenGrok (https://github.com/oracle/opengrok) is also rather well known, but I have found it to have a slightly worse UI than alternatives.
-
Firefox 113.x quietly adds new Linux system requirements
Try using Searchfox to find references to those libraries. When you open a result, hover your mouse over the left column to see what commit added each line.
- Fetch API Implementation source
-
How to find the name of elements for firefox css
You might want to lokk at this, and this, and this .
- What environment variables does Firefox need on Linux?
-
Does this CSS rule crash anyone else's firefox?
Layout is hella broken, obviously, but it doesn't crash. You can do a search for progresschunck at https://searchfox.org to find what it means.
-
Swipe to navigate arrow indicator
https://searchfox.org/ should be you go-to tool to search Firefox code-base.
-
How to apply some css changes only to one (firefox's dark) theme?
Also, you can use browser toolbox to inspect Firefox UI and see what styles are being applied to it and to figure out what selectors to use. Of course, there is also https://searchfox.org/ for when you need to figure out exactly how Firefox is doing some feature x.
cs
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
That’s one of the reasons I made this actually https://github.com/boyter/cs
I wanted and boolean syntax mixed with fzf instant search. It’s not as fast as ripgrep of course but it’s not solving the same problem.
- Sourcegraph is no longer Open Source
- codespelunker
- cs: command line codespelunker or code search written in Go
- codespelunker (cs) A command line search tool. Allows you to search over code or text files in the current directory either on the console, via a TUI or HTTP server, using some boolean queries or regular expressions.
- Show HN: Codespelunker a command line search tool
-
Lmgrep: Lucene-based grep-like utility
Neat. This is similar to a tool I have been working on (but need to finish off) as I saw the same issue.
Except rather than build an index I brute forced the search each time. For most repositories it’s fast enough even with ranking.
https://github.com/boyter/cs For those interested it’s still very WIP with noticeable issues in TUI mode.
-
Ask HN: What Are You Working On?
A few things.
An implementation of bitfunnel search in Go which I plan to put into searchcode.com at some point once I get all the issues resolved and if performance is acceptable
A command line search tool which brute forces with search ranking https://github.com/boyter/cs/ mostly for code but works pretty well for other things as well
Atlassian Confluence Cloud plugins. Mostly out of personal interest and because there appears to be a good marketplace to produce mostly passive income there.
What are some alternatives?
opengrok - OpenGrok is a fast and usable source code search and cross reference engine, written in Java
git-peek - git repo to local editor instantly
hoogle - Haskell API search engine
dcs - Debian Code Search (codesearch.debian.net) is a search engine that searches through all the 130 GB of open source software that is included in Debian. Supports regular expressions!
sourcegraph - Code AI platform with Code Search & Cody
hound - Lightning fast code searching made easy
chrono - Date and time library for Rust
ctoc - Count Tokens of Code (forked from gocloc)
codesearch - Fast, indexed regexp search over large file trees
lucene-grep - Grep-like utility based on Lucene Monitor compiled with GraalVM native-image
livegrep - Interactively grep source code. Source for http://livegrep.com/