NetHack VS ripgrep

download NetHack sources (https://github.com/NetHack/NetHack -> Code -> Download ZIP, unpack them on your computer)

My configuration of Eglot is simple: (use-package eglot :hook (c-mode . eglot-ensure)). And it works for a single c file. But when I use this setup to read the code of NetHack, it doesn't work for linting and definition finding (M-.), even though eglot connection has no problem. I observed the same problems when reading the code of SQLite. Some specific problems I observed:

Since nethack 3.1.0, the source for nethack's "bestiary" has been dat/data.base, in plain text, processed into a file named "data" when building the program. The unprocessed file intended for the nethack's next version can be seen at https://github.com/NetHack/NetHack/blob/NetHack-3.7/dat/data.base (it's quite long).

I am not really 100% sure what you are looking for. Are you looking for the actual picture? It is built during compilation from this uuencoded file https://github.com/NetHack/NetHack/blob/NetHack-3.7/win/win32/splash.uu

xNetHack is based on NetHack 3.7.0, and there was a bug (now fixed) in NetHack 3.7.0 that caused stair destinations to be messed up after a game is recovered. I wonder that has happened here: perhaps you are playing a version of xNetHack that inherited the bug from NetHack 3.7.0, this is a recovered game.

They won't be afraid of music in 3.7.

This is a bug that was fixed in the upcoming 3.7, in this commit. Basically, if the random filler created a space that was made inaccessible by the fixed level design getting overlaid on top of the random filler, a door could be created to make that space accessible.

There is not a comprehensive list of changes in existence. This one comes close but doesn't contain everything https://github.com/NetHack/NetHack/blob/NetHack-3.7/doc/fixes3-7-0.txt

I have an open github issue requesting that intrinsic invisibility be made only temporary, not permanent. That would make the invisibility mechanic more interesting since you could decide multiple times per game whether you want it, and extrinsic invisibility items would become more useful.

ripgrep - https://github.com/BurntSushi/ripgrep

Basic code searching skills seems like something new developers are never explicitly taught, but which is an absolutely crucial skill to build early on.

I guess the knowledge progression I would recommend would look something kind this:

- Learning about Ctrl+F, which works basically everywhere.

- Transitioning to ripgrep https://github.com/BurntSushi/ripgrep - I wouldn't even call this optional, it's truly an incredible and very discoverable tool. Requires keeping a terminal open, but that's a good thing for a newbie!

- Optional, but highly recommended: Learning one of the powerhouse command line editors. Teenage me recommended Emacs; current me recommends vanilla vim, purely because some flavor of it is installed almost everywhere. This is so that you can grep around and edit in the same window.

- In the same vein, moving back from ripgrep and learning about good old fashioned grep, with a few flags rg uses by default: `grep -r` for recursive search, `grep -ri` for case insensitive recursive search, and `grep -ril` for case insensitive recursive "just show me which files this string is found in" search. Some others too, season to taste.

- Finally hitting the wall with what ripgrep can do for you and switching to an actual indexed, dedicated code search tool.

live grep: ripgrep

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

I'm not clear on why you're seeing the results you are. It could be because your haystack is so small that you're mostly just measuring noise. ripgrep 14 did introduce some optimizations in workloads like this by reducing match overhead, but I don't think it's anything huge in this case. (And I just tried ripgrep 13 on the same commands above and the timings are similar if a tiny bit slower.)

[1]: https://github.com/radare/ired

[2]: https://github.com/BurntSushi/ripgrep/discussions/2597

Explore o Ripgrep no repositório oficial: https://github.com/BurntSushi/ripgrep

🔎🗃️ ripgrep or ugrep (search fast, use regex patterns or fuzzy search, pipe output to bash/zsh shell for further processing V coloring)