user_example VS ripgrep

Hey everyone! I'm relatively new to Lua and Neovim. I'm trying to switch over from VSCode to Neovim but before I do I'd like to bring over all of my custom snippets from VSCode. I have a custom user config I made from this template https://github.com/AstroNvim/user_example and I was following these instructions on the AstroNvim docs https://astronvim.com/Recipes/snippets. After following those instructions I tested my snippet in another project I have and the snippet wasn't showing up in my completion options. Given that I'm new to Lua and Neovim I'm not quite sure how to go about debugging the issue. If anyone knows what I did wrong or can at least help point me in the right direction it would be much appreciated! you can check out the code from my configuration here: https://github.com/joegoggin/goggin-nvim/tree/feature-snippets/snippets

I cannot comment on threads older than 2 weeks https://news.ycombinator.com/item?id=10199405

So reply to this https://news.ycombinator.com/item?id=35164665

After cloning astrovim as `~/.config/nvim`, do similar with https://github.com/AstroNvim/user_example but with button "Use this template".

Then in `~/.config/nvim/user/plugins/user.lua` add

```

hey can someone google the link to the docs for me... sure i can... https://astronvim.com/Recipes/custom_plugins lol... you might also want to use the recommended https://github.com/AstroNvim/user_example too <3

hey just ran into this while trying to debug this same issue. I had based my settings on https://github.com/AstroNvim/user_example (just cloned and started editing init.lua), and for some reason setting plugins in init.lua doesn't work if you do that. I started again without cloning the repo and didn't have that issue, plugins worked just fine.

I'm trying to override a highlight group to change its color, to make bash syntax easier to read (for me), but I can't figure out how to make a permanent change in my config, which I splitted following the https://github.com/AstroNvim/user_example template.

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)