rofi VS Waybar

I am using arch linux. For me github is loading very slow and sometimes web pages are not loading properly. For ex this github repo - https://github.com/adi1090x/rofi keeps on loading and even after loading some images (like the drop down images) doesn't load properly. Only facing this problem with github and no other websites. Tried to go to github on my mobile (jio) and facing the same problem. Anyone having the same problem ?

You can look at this link, https://github.com/adi1090x/rofi, for a bunch of different customizations for it if you don't want to make your own.

You can use rofi and custom launchers: https://github.com/adi1090x/rofi

Then there's a tool named rofi, which has zillions of scripts ready to use: https://github.com/adi1090x/rofi

Install rofi and copy the scripts you like. Just a 4 examples it can do: https://www.youtube.com/watch?v=v8w1i3wAKiw just copy any of the zillions scripts and use them: https://github.com/adi1090x/rofi the advance of using rofi is that if you switch distro/WM/DE you just copy paste your configuration files (dotfiles) from your existing install to the new one and everything will work like they used to work.

I'd warmly recommend to start learning to use rofi-menu + sxhkd no matter which distro/WM you use, because that combo has endless opportunities even if you just copied the scripts already in Github: https://github.com/adi1090x/rofi

After multiseat feels too normal, take a look at rofi-menu. Once you understand it's glory it'll will follow you into any Linux install you make in the future. Scripts ready to use in github: https://github.com/adi1090x/rofi

If I understand https://github.com/Alexays/Waybar/wiki/Configuration correctly, what is to be displayed is defined in a JSON file that can be located in one of the directories mentioned.

GNU calls their extensions "equivalent to" things I'd have suggested trying ($_I or $-l), but I'm not sure if the equivalents are themselves GNU extensions, too. Regardless, reading this Waybar Github issue about %OI, I get the impression there was a regression at some point, in any case on March 27th 2022 someone says it "used to work fine until recently".

hope it helps. source btw: https://github.com/Alexays/Waybar/issues/2177

{ config, pkgs, ... }: { wayland.windowManager.sway = let patchedWaybar = pkgs.waybar.overrideAttrs(prev: final: { patches = [ (pkgs.fetchpatch { url = "https://github.com/Alexays/Waybar/pull/2134.diff"; sha256 = "1hzdv3b8zzps50pdcb8pj9cxwaix4q2d4gsqb9dl9vflgl429hq3"; }) ]; }); in { enable = true; config.bars = [{ statusCommand = "${patchedWaybar}/bin/waybar"; }]; };

See this issue. CSS and only new properties in config are reloaded when SIGUSR2 is triggered.

I think this has just been added to waybar (wlr/workspaces) to work in a similar manner to how it is in sway/workspaces. No need for fake empty terminals. Something was merged for wwlr/workspaces in the waybar github. See - https://github.com/Alexays/Waybar/pull/2089.

Ah, well in looking at their git, it appears some do have fallback font issues. See here - https://github.com/Alexays/Waybar/issues/215