Hacker News Reader

Comment by Recursing | Hacker News Reader

> If you are coming from i3 the move to sway is a no-brainer

I was thinking of waiting another year to jump as I'm having no issues with i3, what are the advantages?

Sway has nicer configuration for multihead display setups than you ever get with xrandr, which is very nice on laptops if you often connect to different external monitors. There's also some clunky support for moving windows around with the mouse, which I've found to be occasionally useful.

Then there are the wayland advantages: very little screen tearing if any, no blanking the screen when connecting to a new display, better security properties.

There's disadvantages as well. There's no xdotool support, and if you want to use any sophisticated keybindings or remapping keys, you'll be forced to rely on Sway's configuration language to do that for you. On i3 I was able to bind ctrl_r to right click, but that is — as far as I know — not possible on sway without rewriting the libinput event stream, which is very painful.

  There's no xdotool support

Have you looked at ydotool?

https://github.com/ReimuNotMoe/ydotool

Also, do you know about the "i3 Migration guide"?

https://github.com/swaywm/sway/wiki/i3-Migration-Guide

Given the need to access /dev/uinput as a, user doesn't this require negating the supposed security gains of wayland?

Also not exactly maintained

>Since Jun, 2019, I have little time to maintain this project because I'm striving to start an undertaking (instead of working 996).

You can implement a xdotool's equivalent by using virtual-keyboard and virtual-pointer Wayland protocols.

Can you use `bindsym ctrl+r seat - cursor press button2, seat - cursor release button2`?

Sorry, I was unclear. By ctrl_r I meant the right ctrl key, pressed on its own with nothing else. Binding Ctrl+r might be possible. It's also been about a year since I last tried, so there may be a solution now.

Reply on news.ycombinator.com