wl-clipboard VS Waybar

> things it doesn't support like xclip

https://github.com/bugaevc/wl-clipboard

$ cat ~/bin/clip

    #!/bin/sh

With the default config I noticed I couldn't paste contents from the selection buffer in some applications, so I added the following wl-clipboard calls in my hyprland.conf:

This is just kinda how wayland works. The way wl-clipboard handles it is it forks off and stays in the background. That process is what serves the clipboard requests.

On wayland wl-paste pastes the from the clipboard. On X11 replace wl-paste with either xsel --clipboard --output or xclip -selection clipboard -o

No, but there's a wl-clipboard for that

Linux isn't very pleasant.

> choosing to have vsync enabled or disabled in games

See this thread? https://www.reddit.com/r/swaywm/comments/ntszm9/how_can_i_ma...

I'm not 100% sure what you're asking.

> EDIT: I should another important one for me: xclip, read from and write to the clipboard in the command line

https://github.com/bugaevc/wl-clipboard

I just had a quick Google and xclip or wl-clipboard may be what you’re looking for. I’ve never used them but they sound promising.

For point 2 I found that wl-paste seems to share the windows clipboard. Taking a screenshot and then in WSL

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