You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pretty sure there's definitely a way to do this but using the for window [ app id ] etc; then using for example border pixel 1 or border none doesn't remove the image borders.
I tried it without the image border ( on this fork just using normal border) and it worked fine.
sway version 1.5-64ea407f (Dec 18 2020, branch 'master')
for_window [app_id="avizo-service"] floating enable, border none
This removes the border if i'm using normal borders but not when I'm using the images. I'm guessing there's perhaps another variable I should use but it's not documented....
I'm hesitant to call this a bug in sway-borders because this is knowingly left out. border_images apply generally to all containers/views and not individually to containers like the standard border pixel.
In this case, avizo shouldn't be asking to have borders drawn in the first place. I don't know much about Wayland, but I believe it should be using the layer-shell protocol, for which Sway won't draw borders for. Most notification daemons, bars, etc. use it.
Overall though, I think it would be great to support per-container border_images, so I'll leave this up as a feature request.
I'm pretty sure there's definitely a way to do this but using the
for window [ app id ] etc;
then using for exampleborder pixel 1
orborder none
doesn't remove the image borders.I tried it without the image border ( on this fork just using normal border) and it worked fine.
sway version 1.5-64ea407f (Dec 18 2020, branch 'master')
for_window [app_id="avizo-service"] floating enable, border none
This removes the border if i'm using normal borders but not when I'm using the images. I'm guessing there's perhaps another variable I should use but it's not documented....
Some relevant part of my config.
If it helps.
The text was updated successfully, but these errors were encountered: