2 ms·
Not sure why you are getting down-voted. I use a window manager that has no Wayland support, so I am not switching anytime soon either. Perhaps I will when and
by johnisgood 6y ago
Not sure why you are getting down-voted. I use a window manager that has no Wayland support, so I am not switching anytime soon either. Perhaps I will when and if it ever gets Wayland support, but for now, everything works on my end with Arch Linux. I also have "~/.xinitrc", "~/.Xdefaults", and I use "startx" to start my window manager. I have absolutely no clue how to have the equivalent of those in Wayland, including "xsetroot", "xset", and "setxkbmap", among a lot of other stuff, but that is due to my ignorance, so if anyone knows, lead the way please. :)
- cfcosta 6y agoDepends on what you plan on use when you do make a switch. In general, X applications will keep using Xdefaults because they run on XWayland, and the window manager will handle input configuration, displays, wallpaper and so on. There are some ad-hoc implementations for doing what you want iirc, but it really is more "integrated" than what you are used for. I have to test, have not done that in quite a while, but I think that you can just call let's say "sway" on the CLI and it will start wayland directly.