espanso VS ripgrep

If you want a standalone cross platform text expander I currently enjoy using Espanso[1]

[1]: https://espanso.org/

# espanso match file # For a complete introduction, visit the official docs at: https://espanso.org/docs/ # You can use this file to define the base matches (aka snippets) # that will be available in every application when using espanso. # Matches are substitution rules: when you type the "trigger" string # it gets replaced by the "replace" string. matches: # signatures - trigger: ";n" replace: "Nikola" - trigger: ";b" replace: "Brežnjak" - trigger: ";li" replace: "https://www.linkedin.com/in/nikola-bre%C5%BEnjak-892b9a24/" - trigger: ";sn" replace: "Kind regards,\nNikola Brežnjak\nhttp://www.nikola-breznjak.com/blog" - trigger: ";web" replace: "http://www.nikola-breznjak.com/" - trigger: ";em" replace: "[email protected]" ## git - trigger: ";ga" replace: "git add ." - trigger: ";gb" replace: "git branch" - trigger: ";gc" replace: "git commit -m " - trigger: ";gd" replace: "git diff --color " - trigger: ";gf" replace: "git fetch --all" - trigger: ";gi" replace: "find . -name '.DS_Store' -type f -delete" - trigger: ";gl" replace: "git log" - trigger: ";gp" replace: "git push origin main" - trigger: ";gs" replace: "git status" - trigger: ";gt" replace: "git remote -v" - trigger: ";gu" replace: "git pull origin main" ## blog - trigger: ";bimp" replace: "https://nikola-breznjak.com/blog/books/want-improve-read-books/" - trigger: ";brem" replace: "https://nikola-breznjak.com/blog/miscellaneou/make-remote-developer/" ## emojis - trigger: ";eew" replace: "⚠️" - trigger: ";eet" replace: "🤔" - trigger: ";eeb" replace: "💰" - trigger: ";eem" replace: "💪" - trigger: ";eetm" replace: "™" - trigger: ";eeh" replace: "❤️" - trigger: ";eeu" replace: "👍" - trigger: ";eep" replace: "🙏" - trigger: ";eef" replace: "🤦" - trigger: ";ees" replace: "🙂" - trigger: ";eeg" replace: "😎" - trigger: ";eev" replace: "👋" - trigger: ";eel" replace: "😂" - trigger: ";eec" replace: "👏" - trigger: ";eeo" replace: "✅" - trigger: ";eer" replace: "🚀" - trigger: ";eex" replace: "⏭️" ## replies - trigger: ";ryw" replace: "You’re welcome 👍" - trigger: ";rlmk" replace: "Please let me know 👍" - trigger: ";rbtw" replace: "Btw, how are things on your end?" - trigger: ";rt" replace: "Thank you! 👍" ## misc - trigger: ";fd" replace: "firebase deploy" - trigger: ";wed" replace: "Happy Wednesday (a dy on which, historically, most people wed on - thus: Wed nes day). Not really, but it would be a fun fact actually 🙂" - trigger: ";cl" replace: "console.log(" - trigger: ";se" replace: "select * from " - trigger: ";o" replace: "open ." - trigger: ";im" replace: "" vars: - name: "clipb" type: "clipboard" - trigger: ";ch" replace: "chrome://history" - trigger: ";;c" replace: "code ."

This should work for you. Free, cross-platform and works everywhere not just the browser. https://espanso.org/

Huh, didn't know abbrev had that limitation (wonder why?). Gave it a go in espanso (https://espanso.org/), and it does work there.

I use a tool called "Espanso" to accomplish something similar at work. It only runs locally, so no weird data scraping issues to worry about. And it's easy to update as things changes becauase everything lives in a simple yml file.

https://espanso.org/

It can do simple text replacement, so I have words, phrases, and sentences I use frequently compressed into a few keyboard clicks. It can also grab what is in your clipboard, so that can be incorporated into responses, which is simple but very handy.

A simple text replacement looks like this in the yaml file:

If you don't know what a text expander is, see: https://espanso.org

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)