Hyprland VS ripgrep

I've been wanting to try http://hyprland.org/, but since plasma gets me far enough and provides a working taskbar (wifi, sound, bluetooth, mount, clipboard) and virtual desktops on which I end up opening just firefox and emacs I haven't really given it a chance.

Hyprland builds using a pinned commit of wlroots instead of a tagged release because wlroots release schedule is too slow for Hyprland's development [0]

This turns into a problem for maintainers because many distributions refuse to ship non tagged versions of software

Hyprland used to depend on wlroots-git, but when it made the switch to use specific pinned commits a lot more distributions started to package it [1], but some still refuse to do so such as Debian.

[0] https://github.com/hyprwm/hyprland/issues/302#issuecomment-1...

[1] https://gitlab.alpinelinux.org/alpine/aports/-/merge_request...

I have Hyprland a try some weeks/months ago, and seemingly it had a video memory leak where after some hours of usage, it ended up taking more than 5GB of VRAM, with no signs of slowing down.

I found one issue (https://github.com/hyprwm/Hyprland/issues/1504) mentioning something similar, but it was closed and I was still experiencing the same issue, so not sure what's going on.

Gnome3 doesn't manifest the same issue, so worth checking out if it happens to you if you're curious about moving from Gnome to Hyprland.

I've been an X11 holdout since forever, but after nvidia proprietary drivers broke for the millionth time on a system upgrade, I switched over to Nouveau and the "Hyprland" tiling compositor on Wayland. It's the only setup that felt worth the upgrade to me. Setup was easy, animations are very slick (scroll down on the link below for a sample), and I've had no bugs or quirks. Highly recommend checking it out if you're bored or curious.

https://hyprland.org/

I did some research as far as I know there isn't really a way for it to have a transparent window but not transparent text although I found this, basically change the opacity of the window/program. You can also set active and inactive opacity on the window if that's any help.

# Monitor Configs # source https://wiki.hyprland.org/Configuring/Monitors/#general monitor=,preferred,auto,1 # for pluggin' in random monitors monitor=,highrr,auto,1 # prefer high refresh rate for all monitors input { kb_layout= kb_variant=ffffff kb_model= kb_options=compose:rctrl,level3:ralt_switch kb_rules= follow_mouse=1 touchpad { natural_scroll=yes disable_while_typing=true scroll_factor=1 } } misc { disable_hyprland_logo=true animate_mouse_windowdragging=false # this fixes the laggy window movement (source: https://github.com/hyprwm/Hyprland/issues/1753) animate_manual_resizes=false # fixes slow resizes } general { #sensitivity=1.0 # for mouse cursor gaps_in=8 gaps_out=15 border_size=4 col.active_border=0xfff5c2e7 col.inactive_border=0xff45475a col.group_border=0xff89dceb col.group_border_active=0xfff9e2af apply_sens_to_raw=0 # whether to apply the sensitivity to raw input (e.g. used by games where you aim using your mouse)

Therefore I am considering switching to hyprland-nvidia-git, but when I look at its AUR page (https://aur.archlinux.org/packages/hyprland-nvidia-git) it says 0.31 as the version, whereas the latest version is 0.32 (https://github.com/hyprwm/Hyprland/releases). I thought the git package would be cutting edge "automatically", but perhaps I'm missing something...?

This is what I've found so far:

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)