denote VS ripgrep

Where I define shortcuts for different action p for project actions (Pressing SPC - p opens project actions) , n for denote and so on. And for denote for example I do something like this:

The denote page is here, https://protesilaos.com/emacs/denote , and the code can be acquired on github https://github.com/protesilaos/denote

So, if you want to contribute to bringing the signature feature to the main branch, you can work with it for a while and relay your experience and use cases to the discussion on github.

Yesterday, somebody found out that filetags do share some similarities with Prot's denote which is discussed here: https://github.com/protesilaos/denote/issues/117 You might want to read that as well. I added a comment with a few remarks how I'm using the concept within Emacs Org mode.

I am in the same boat. I have never been able to shake the feeling that org-roam is unnecessarily complex and reinvents the wheel a bunch; which might or might not be true, but for all my use cases so far, I haven't needed/used a feature that warrants so many moving pieces. I have a todo item to move my notes from org-roam to denote instead, which I am eyeing for its apparent simplicity.

Try denote. I use it a lot, Im happy with it.

The GitHub for it is here: https://github.com/protesilaos/denote

I'm not sure if you are aware of the denote package brewing right now! https://github.com/protesilaos/denote

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)