scripts VS ripgrep

Check out Vermaden's site: https://vermaden.wordpress.com/

I mostly do interesting stuff on FreeBSD and its all documented in as detailed form as possible here:

- https://vermaden.wordpress.com/

Regards,

You might want to check out Vermaden https://vermaden.wordpress.com/ And Robonuggie https://youtube.com/@RoboNuggie Both excellent resources on how to get things done on the desktop in FreeBSD. Salute

I always wanted to start and write on my blog - just to share some things that other may find useful.

I started with something simple - entirely preloaded (all howtos) and static:

1. http://www.strony.toya.net.pl/~vermaden/links.htm

I assume no one ever entered it ... besides me of course.

Then some time later - I though that having that 'static' links site is pointless - lets start 'proper' blog this time. I have chosen Gogle Blogspot this time.

2. https://vermaden.blogspot.com/

... and after several posts I generally abandoned it.

Several years later I made a decision to make another blog ... but this time with some strategy behind.

3. https://vermaden.wordpress.com/

This (3rd) attempt was 'successful' and people sometimes actually visit my blog - sometimes even comment. In March of 2023 I will 'celebrate' the 5th year of that blog. I have made about 100 posts there and I made about 100,000+ views per year:

- https://i.imgur.com/raWvrZj.png

What is the secret of [3.] being successful and [1.] and [2.] definitely not? Sharing.

I do not know what blog (subject matter) you are trying to share - but for IT/UNIX/BSD/Linux related blogs (as mine) you need to share each post on these mediums:

- mastodon

- twitter

- lobsters

- hacker news

- FreeBSD forums

- reddit (r/BSD)

- reddit (r/FreeBSD)

- reddit (r/unix)

- reddit (r/linux)

- linkedin

Not sure about Facebook/Meta as their 'ecosystem' definitely does not suit my needs.

You need to ask yourself where and how people would try to find your content. They would definitely not browse a catalog of blogs. Maybe they wil ltry the search engine ... but search engines only pick up sites that are somewhat popular. They omit pages/blogs that are 'unknown'. How blogs are known? By many links pointing to them.

In other words - if you do not share your work/posts on all 'relevant' platforms - then you will 'die' in a 'non-known' hell.

If you believe your work - and it is work, you 'waste' your time to write/share these things you do - is valuable - then share them in all possible mediums/medias. If your content is good - you have to do nothing else. If your content is crap - You will immediately get feedback about it :D

One of the things that I really appreciate was the feedback I got. I often assumed that I know a lot about 'X' topic - just to change my mind after several comments later and providing and UPDATE to my blog post :)

I do not know what should I add here more so I will end my comment - but feel free to ask if You have any questions.

Regards,

After you get it all running using the cooltrainer site, then go to https://vermaden.wordpress.com/ which has some most excellent tasty config changes to make your boot time shorter, and your desktop work better. ALONG with tons of configs to help you configure different desktops and desktop apps/configs.

Any suggestions on how to get resume to work after suspending on a Thinkpad X260? I have read https://vermaden.wordpress.com/ and got suspend to work it just locks and have to reboot.

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)