This is why I dislike Wayland. Forcing so much functionality through the WM means I can't just build my system out of small parts. I also do things that Wayland is specifically designed to break, like keylogging myself.

I agree with your first point against Wayland, but your second point isn't correct: Wayland's design is not meant to prevent keyloggers just to make them optional.

Same problem, really: now I have to find a window manager that natively supports key logging, rather than just running a small shell script in the background that listens for keyboard events.

Understandable. One of the reasons I haven't switched is because so far my system works pretty well and I haven't had the need to use Wayland. What hotkeys do you use sxhkd for? I vaguely remember sxhkd supporting chords while i3 not doing so, but I don't remember more than that.

I use i3wm's `bindsym` for stuff that's related to window management, like moving around windows, resizing them, moving windows or focus to workspaces, etc. Other stuff, like volume control, screenshots (print screen -> take screenshot, upload to a web server, put URL in clipboard), mouse movement (with xdotool), etc. is handled through sxhkd. There's no reason I couldn't just use bindsym for all of that, but now non-windowing hotkeys is not coupled with the WM, so I could choose to switch window manager and still have all non-WM hotkeys work.

Sounds interesting. Could you share your setup/workflow?

Here's my git repository with all dotfiles and such: https://github.com/mortie/nixConf

I use i3wm (well, i3-gaps) as the WM. Xdotool is just used to move the cursor with hotkeys: https://github.com/mortie/nixConf/blob/7c12d4215c703de0c6935..., scrot is used both for a print screen button (scrot takes the picture, then it's copied to my server with scp, and the URL is put in the clipboard: https://github.com/mortie/nixConf/blob/master/bin/mshot) and for i3lock (scrot takes the picture, imagemagick pixelates, i3lock shows it: https://github.com/mortie/nixConf/blob/master/bin/mlock).

I also have a project called dedaemon: https://github.com/mortie/dedaemon. That uses udev to listen to events, like displays or input devices being connected or disconnected, and does a preconfigured to them. I for example have these lines, which sets the resolution and frame rate to any connected monitor to the highest possible, and positions it to the left of the primary monitor: https://github.com/mortie/nixConf/blob/7c12d4215c703de0c6935.... I imagine porting that functionality to wayland would be really hard, and probalby require writing custom extensions to each window manager separately.

There's also this other project I have, which isn't really related to wayland, but which I still feel is relevant: mmenu - https://github.com/mortie/mmenu. It just makes dmenu work as a calculator, running the input through python if it doesn't match a program in your $PATH, plus some other features.

Thanks for sharing! I really appreciate it. Already "borrowed" the screen lock solution, and will look into other productivity enhancements :)

You sound like someone who'd like keynav http://www.semicomplete.com/projects/keynav

Since it wasn't linked last time I looked, code is also at https://github.com/jordansissel/keynav

Shameless plug: I maintain a fork at https://github.com/yjftsjthsd-g/keynav because the original author hasn't been active in a while.

Edit: wrong link :)

That looks pretty interesting. stole the idea and made something similar in bash: https://github.com/mortie/nixConf/blob/master/bin/mousetree, with hotkeys configured with sxhkd: https://github.com/mortie/nixConf/blob/d87f241963edc49a57171...

Not so shameless if you add a scroll functionality I tell you lol.

Actually even otherwise, it's not like you're earning money so no need to disclaim!

Heh, so I went to look and see how hard it would be to simulate mouse scrolling, and the answer is... none. Literally none. Because X11 "mouse scroll" events are represented as button presses. Mouse buttons are 1=left, 2=middle, 3=right, 4=scroll-up, 5=scroll-down. So you just stick the relevant lines in your keynavrc; ex.

   i click 4                                                                                                                             
   e click 5                                                                                                                             

That said, I may make an effort to document this better.

I saw, I came here to thank and noticed you replied :)

Hm. That would be useful. I might have to do that.