Tiling Window Manager Thread

Just set it in your config to open firefug/whatever in Workspace 2.

kill yourself tripfag. monokai on Atom on my MacBook Pro is the best color scheme.

kys

Theres literally nothing wrong with it. Far better than having one open next to the other.

stop impersonating me

>Steve Klabnik !Steve.RD..

I've only tried sway and way-cooler 3 months or so ago only to go back to i3wm+Xfce goodies.
Sway would slow down to a crippling halt as I opened more windows but otherwise almost identical to i3. Way-cooler was pretty smooth and snappy can't recall the issues I had with it most likely related to multi monitor support.
In both cases I couldn't for the life of me find a function similar to xrandr to rotate one of my displays.

I don't have any major problems with Xorg after fixing the horrible screen tearing.
Still waiting on wayland to mature and support GPU hotswapping with a decent tiling manager at least on par functionally wise with i3. I use my dedicated GPU on both host and guest interchangeably.
Would be great to switch between my iGPU and dGPU without logging out and loosing my current session whenever I want to boot up a windows VM with GPU passthrough since I always have my dGPU bound to host OS when not using a VM.

Speaking of which, I'd hate to impose but I do have an annoying issue I couldn't find an online solution to that happens only after I use i3-logout with tty1 set to autologin.
Xorg or i3 workspaces plugin would hit 100% cpu usage on a single core it is either one or the other and sometimes an application such as qbittorrent does not show up in the icon tray although its process exists.
Currently I have to manually intervene by killing the process using 100% cpu and kill/restart qbit. if it is Xorg at 100% the login process is repeated after killing it after which I have to kill the i3 workspaces process which is now at 100% cpu and kill/restart qbit.
Not the biggest deal in the world but It does get irritating.

Anyone else try bspwm? It is very respectful of the unix philosophy. It does one thing and does it well, which is manage windows. It does not accept input. Instead, you use a keybinding daemon called sxhkd to do that. Sxhkd does one thing and does it well, which is run commands when certain keys are pressed. Also, you install your own bar as a separate thing, rather than having one come with it like i3 or awesome. It all adds up to a system that is low on bloat and ram usage, and once you get it configured, high on comfy. It goes well with a systemd-free distro of your choice.

Also you don't need a shitty fork to get gaps support.

How did you bloat your system this hard?

>I'm running Void with i3 and my startup memory usage is