You've got multiple monitors and watch to switch to a window several windows away.

You could switch focus there with a number of arrow key movements.

"sway-easymotion" allows you to use to press a key that prints a one or two character label on each window. Press that key and your focuses switch there.

Over the weekend I submitted patches for a couple of new features. First, I added multi-monitor support. Second, I added a visual confirmation of which window was selected.

If you are familiar with Github and Rust, you can review the patches and try them out here:

https://github.com/edzdez/sway-easyfocus/pulls

More about sway-easyfocus: https://github.com/edzdez/sway-easyfocus

cross-posted from: https://lemmy.world/post/29689984

I use i3. I have a machine coming that only work with Wayland, so I'll be installing Sway on it.

I know Sway is touted to be a drop-in replacement for i3, but the more I think about it, the more I wonder how much of this is true.

Like for example, all the key bindings use X11 keysym names. Or the window properties likes Class and Title are also X11-specific. Surely none of this applies to Wayland, correct?

I recently upgraded from an RX 570 to an RX 6600. Everything is working great, except that the font in my menu program Fuzzel as well as the font in my terminal foot is really big on one monitor and the correct size on the other monitor. I thought it might be because the monitor with the big text had a displayport to hdmi adapter, but I switched that monitor to hdmi and the other monitor to dp, and the same monitor still had big font in the menu and the terminal. The scaling seems to be correct, both monitors seem to be identical. What is going on? Any ideas? I'm running Debian Bookworm. I also installed the amd drivers as instructed on the Debian Wiki.

Thanks

cross-posted from: https://lemmy.world/post/26945293

cross-posted from: https://lemmy.world/post/26517981

I've been suggested to use a tiling window manager like Sway since it allows for controlling windows with hotkeys, but I'm having trouble getting started. I installed it in Fedora and tried logging back in with SwayFX (since it has features like blurring) but after I'm just shown a wallpaper with a top bar, the top left shows a 1 and the top right shows the time. I don't know what to do there. I tried looking up guides but didn't find anything, can you link me some if you know of any?

cross-posted from: https://lemmy.world/post/24599872

I love i3wm and would like to switch to sway for the advantages of not using xorg. But is it worth it with a laptop that has an old nividia/intel hybrid video card? I had read that it was complicated to use nvidia cards with wayland

I miss the keyboard friendliness of HUDs and how you could search the menu quickly.

I was wondering if anyone had a wofi/rofi or equivalent HUD for sway.

Back in the day there was plotinus. So far I can't get plasmahud, gnomehud, rofihud or others to work.

I noticed this immediately because I use kanshi (highly recommended for laptops running sway!). I don't know the how or why (maybe it's the wlroots bump), but when I upgraded Sway to 1.9 today, the Hex ID form one of my external monitors changed. So I had to update it in the config for kanshi to work again.

Just a heads up for other kanshi users, and people whose scripts may be influenced by this.

So I migrated from i3 to sway. Had a python script that I found on the internets that did this, and really like the functionality. Figured I'd give an attempt at making my own script in bash. My programming skills and bash scripting aren't great, so I had chatGPT help me with some syntax. Thought others might be interested so am sharing here.

#!/bin/bash

# this script moves a container to an empty workspace
#  and switches to that workspace

# Define list of available workspaces
all_workspaces_list=(1 2 3 4 5 6 7 8 9 10)

# get workspaces currently being used
used_workspaces=$(swaymsg -t get_workspaces | grep -oP '"name": "\K\d+')
# create a list from used workspaces
used_workspaces_list=($used_workspaces)

# Check for first of all_workspaces_list not in used_workspaces_list
for workspace in "${all_workspaces_list[@]}"; do
    if [[ ! "${used_workspaces_list[*]}" =~ "$workspace" ]]; then
        free_workspace=$workspace
        break # stop loop after finding first available workspace
    fi
done

swaymsg move container to workspace number $free_workspace
swaymsg workspace number $free_workspace

Okay, I am super new to tiling windows managers, and let me just say - Sway made me an instant convert. I'm obsessed. But I still have no clue what I'm doing.

So I have been trying out every status bar I can to see what looks good, what feels good, and what has the best efficiency for some of my SUPER low-grade hardware.

This brings me to yambar. It is touted as the most resource efficient status bars, and because I only want to see a few things (battery, ram, cpu, volume, time/date), I figured it was a good fit. I downloaded and installed it (used AUR) and I had a few issues getting it installed, but eventually go there. (I should probably say right now that I'm also new to Arch. All my previous Linux experience has been Debian based.)

So now that yambar is installed, I snagged the example config.yaml and moved/renamed it to ~/.config/yambar/config.yaml. Now most of the previous status bars I've been trying required you to add/change something in the ~/.config/sway/config to make them go. usually in between some bar:{status_command }. So I went ahead and tried to add status_command /usr/bin/yambar in there, and I just got errors.

I've read the documentation on yambar's codeberg like 100 times, and there isn't anything in there about how to actually activate this darn bar. I'm guessing I'm missing something totally noob.

Help?

(ps- love the community. Subscribed immediately.)

Hi !

I'm using Firefox Developer edition on sway, and since version 121 it shows a small border on top. I have the option hide_edge_borders both enabled, so this border is displayed by Firefox, not Sway (cf. the terminal on the right end of the screenshot).

Does someone else have this issue? Do you have an idea for a workaround? Is this a bug I should report to Firefox?

PS: I've seen this issue on Arch, NixOS and Firefox 122

Satty has seen a new release v0.2.0. We fixed some bugs, got brand new marker tool and got tooltips (contributed by @noornee).

Check it out:

• Arch Linux: https://aur.archlinux.org/packages/satty-bin
• GitHub: https://github.com/gabm/satty

Let us know what you think and how we can improve :)

I wrote a script and bound it to a key combo so I can draw a rectangle on the screen and map my drawing tablet to that area.

Future improvement: force the mapped area to the same aspect ratio as the tablet. I hope I can find a better way to programmatically get the ratio than running xinput list-devices and parsing out "Size: 160x100mm".

Bound via bindsym $mod+Shift+t exec ~/.config/sway/tablet-map. Is there a better way to reference the way config directory?