
Switching to i3 - Day 12 - Binding Modes DistroTube
video description
Date: 2022-03-30
Related videos
Comments and reviews: 10
Kevin
A useful trick for keybind modes is to chain mode exit message after the completed command. It's useful to bind your more uncommon program executions to another one shot shortcut layer. I use a non-mod key like Menu for it simplify the hand movement and abstract the layer.
If the video shots covered this. Oops. Was cooking not watching.
I can't advise on virtual box as I use qemu command line scripts. Everyone covered my initial ideas short of additionally performing a resize message to a specific resolution in case that helped. Full screen I had the same issues using the i3 fullscreens but not the in-client fullscreens on virt-viewer. I use looking glass for all my serious fullscreens needs though so I've not looked closer.
It seems associated to whether the resized window call gets hit in X. I intended to research other i3-messages or shell script calls to elsewhere to resync it.
This is one reason I planned on looking at DWM so I could just quickly go to low level API did the cornucopia of minutia in tiling WMs like this.
reply
A useful trick for keybind modes is to chain mode exit message after the completed command. It's useful to bind your more uncommon program executions to another one shot shortcut layer. I use a non-mod key like Menu for it simplify the hand movement and abstract the layer.
If the video shots covered this. Oops. Was cooking not watching.
I can't advise on virtual box as I use qemu command line scripts. Everyone covered my initial ideas short of additionally performing a resize message to a specific resolution in case that helped. Full screen I had the same issues using the i3 fullscreens but not the in-client fullscreens on virt-viewer. I use looking glass for all my serious fullscreens needs though so I've not looked closer.
It seems associated to whether the resized window call gets hit in X. I intended to research other i3-messages or shell script calls to elsewhere to resync it.
This is one reason I planned on looking at DWM so I could just quickly go to low level API did the cornucopia of minutia in tiling WMs like this.
reply
budlabs
Derek, i think you can fix the issue with virtualbox non fullscreen windows by setting window rules in the config: for_window [instance=-VirtualBox Machine-] fullscreen. for_window rules works like this: whenever a new window is created, i3 will search for any for_window with a matching criteria and execute any commands -on that window-. But only when once when it is created, if you create a new window matching the same criteria, the rule will ofc apply to that too. You can also do crazy things like this: for_window [CRITERION] fullscreen; exec firefox. notice the semicolon, see how you can chain commands. If you instead use a comma, you can add multiple commands to the same window: for_window [CRITERION] move left, border pixel 10; exec firefox. it's pretty cool, to find the right criterion, you can use wmctrl -lx, or a script i wrote called i3get.
reply
Derek, i think you can fix the issue with virtualbox non fullscreen windows by setting window rules in the config: for_window [instance=-VirtualBox Machine-] fullscreen. for_window rules works like this: whenever a new window is created, i3 will search for any for_window with a matching criteria and execute any commands -on that window-. But only when once when it is created, if you create a new window matching the same criteria, the rule will ofc apply to that too. You can also do crazy things like this: for_window [CRITERION] fullscreen; exec firefox. notice the semicolon, see how you can chain commands. If you instead use a comma, you can add multiple commands to the same window: for_window [CRITERION] move left, border pixel 10; exec firefox. it's pretty cool, to find the right criterion, you can use wmctrl -lx, or a script i wrote called i3get.
reply
stewie410
numlockx and similar can be installed (or scripted; see the Arch WIki on Numlock) for persistent numlock on boot. And my only thought for VirtualBox would be your floating rule. While I've not personally had this issue, it appears that forcing all VirtualBox windows to Float, and then requiring the VM windows to Fullscreen, may be causing an issue with i3. but I'm not sure off hand.
reply
numlockx and similar can be installed (or scripted; see the Arch WIki on Numlock) for persistent numlock on boot. And my only thought for VirtualBox would be your floating rule. While I've not personally had this issue, it appears that forcing all VirtualBox windows to Float, and then requiring the VM windows to Fullscreen, may be causing an issue with i3. but I'm not sure off hand.
reply
Nev
I've used VirtualBox in i3 for a number of years (in Manjaro for the last six months and previously in ubuntu for years) and never had problems like you described. I don't have anything VB related in my. i3/config. Also VMWare and KVM have always worked fine in that regard. They just tile, or tab, or fullscreen like anything else. Thanks for the vid.
reply
I've used VirtualBox in i3 for a number of years (in Manjaro for the last six months and previously in ubuntu for years) and never had problems like you described. I don't have anything VB related in my. i3/config. Also VMWare and KVM have always worked fine in that regard. They just tile, or tab, or fullscreen like anything else. Thanks for the vid.
reply
johnny5finger
These kind of desktop environments are for a very very niche market. I know the benefits of using i3, the question is why. The reason graphical desktops exist, is to let users point and click to run their computers.
With the power of modern computers using i3 doesn't make sense. But if you want to run have at it.
reply
These kind of desktop environments are for a very very niche market. I know the benefits of using i3, the question is why. The reason graphical desktops exist, is to let users point and click to run their computers.
With the power of modern computers using i3 doesn't make sense. But if you want to run have at it.
reply
Martin
I like the philosophy behind tiling desktops but it is really painful to set it up on Ubuntu 18. 04. While i3 has good documentation I think the documentation for the add- ons ( rofi, compton, polybar, etc etc ) are lacking, not up to date or unclear. So prepare for some struggle in order to get working the way you want.
reply
I like the philosophy behind tiling desktops but it is really painful to set it up on Ubuntu 18. 04. While i3 has good documentation I think the documentation for the add- ons ( rofi, compton, polybar, etc etc ) are lacking, not up to date or unclear. So prepare for some struggle in order to get working the way you want.
reply
Garry
Dunno about vbox, I use VMWare. ANWAY. My VM window is just minimized. I access my -virtual box- through SSH and VNC. (Basically I use my VMs as if they were headless.
Use tigerVNC, resizing works well (I use that with Slackware xfce / Arch i3. Finally I find it's the best way to play with VM gui -> VNC.
reply
Dunno about vbox, I use VMWare. ANWAY. My VM window is just minimized. I access my -virtual box- through SSH and VNC. (Basically I use my VMs as if they were headless.
Use tigerVNC, resizing works well (I use that with Slackware xfce / Arch i3. Finally I find it's the best way to play with VM gui -> VNC.
reply
anjelgiofu
Perhaps you'll have some luck either using
$ setleds +caps
or
$ xset led named -Num Lock-
(to turn off: $ xset -led named -Num Lock-)
They don't work on my system, but the internet says they -might- work. Otherwise there's a package, numlockx, available. Seems a bit overkill though.
reply
Perhaps you'll have some luck either using
$ setleds +caps
or
$ xset led named -Num Lock-
(to turn off: $ xset -led named -Num Lock-)
They don't work on my system, but the internet says they -might- work. Otherwise there's a package, numlockx, available. Seems a bit overkill though.
reply
C: \THE
hey DT i had those issues and i added: for_window [class=-virtualbox-] floating enable and for_window [class=-virtualbox-] fullscreen enable, i believe vbox adds some lines to your config file and a # behind it and ad those lines that i shared and it should work: )
reply
hey DT i had those issues and i added: for_window [class=-virtualbox-] floating enable and for_window [class=-virtualbox-] fullscreen enable, i believe vbox adds some lines to your config file and a # behind it and ad those lines that i shared and it should work: )
reply
Alcesmire
Pretty sure your virtualbox floating/fullscreen issues has to do with your i3 config. Probably a for_window that matches too much. The classes you want to match is -VirtualBox Machine- for the VM and -VirtualBox Manager- for the manager.
reply
Pretty sure your virtualbox floating/fullscreen issues has to do with your i3 config. Probably a for_window that matches too much. The classes you want to match is -VirtualBox Machine- for the VM and -VirtualBox Manager- for the manager.
reply
Add a review, comment















