#19 filter windows in switch-workspace 3 days ago

Comment by ~tsdh on ~tsdh/swayr

I guess it wouldn't be too hard to add some --current-workspace flag to switch-window. But as you say, it's probably much faster to use, e.g., swayr next-window current-workspace to switch around the few windows one has on one workspace...

#41 Support for pipewire? a month ago

Comment by ~tsdh on ~tsdh/swayr

Thanks to ~bitraid, swayrbar-0.4.1 has just been released with a new wpctl module.

REPORTED RESOLVED IMPLEMENTED

#43 Use rofi instead because wofi is not on-top in fullscreen mode 2 months ago

Comment by ~tsdh on ~tsdh/swayr

Tassilo Horn referenced this ticket in commit 1e4d39b.

REPORTED RESOLVED FIXED

#43 Use rofi instead because wofi is not on-top in fullscreen mode 2 months ago

Comment by ~tsdh on ~tsdh/swayr

Thanks ~scoopa, I'll add -Dlayer=overlay to the default flags passed to wofi because I see no reason why a window switcher menu should not be on top of fullscreen windows.

#43 Use rofi instead because wofi is not on-top in fullscreen mode 2 months ago

on ~tsdh/swayr

Great. Yea. I will report an issue on wofi.

On 23.09.2024 20:49, ~tsdh wrote:

What is your aim with this ticket? Do you want me to change the default config from wofi to rofi? I don't think I'll do that because it would force me to come up with curated formats including all features (like icons) that work with rofi. And it could break people's existing setup when they didn't override menu.executable and menu.args.

So I think I'll just keep this report open for users to discover.

#43 Use rofi instead because wofi is not on-top in fullscreen mode 2 months ago

Comment by ~tsdh on ~tsdh/swayr

What is your aim with this ticket? Do you want me to change the default config from wofi to rofi? I don't think I'll do that because it would force me to come up with curated formats including all features (like icons) that work with rofi. And it could break people's existing setup when they didn't override menu.executable and menu.args.

So I think I'll just keep this report open for users to discover.

#42 No switch to floating window 4 months ago

Comment by ~tsdh on ~tsdh/swayr

I've released swayr-0.27.4 which uses the new version of swayipc-types where the bug is fixed.

REPORTED RESOLVED CLOSED

#42 No switch to floating window 4 months ago

Comment by ~tsdh on ~tsdh/swayr

The bug on the other side has been fixed, so I only have to wait for a new release of the swayipc-types crate.

#42 No switch to floating window 5 months ago

Comment by ~tsdh on ~tsdh/swayr

Ok, the problem is that the new version 1.3.1 of the swayipc-types crate doesn't return floating nodes in Node::iter(). I've created a bug report there (https://github.com/JayceFayne/swayipc-rs/issues/53) to check if that's intended or a bug.

#42 No switch to floating window 5 months ago

Comment by ~tsdh on ~tsdh/swayr

Oh, sorry, I got confused by another foot window and the fact that swayr get-windows-as-json also seems to ignore floating windows (which isn't expected, too).