You are not logged in.
Since my BL Boron install I've been switching between my 4 workspaces using the mouse. But aren't there also preset keybindings available for this?
I've looked in: ~/.config/openbox/rc.xml. and ~/.config/openbox/bl-rc.xml. and they're both empty. I figured I could create my own but unsure how and if that should be done in one of the above config files or elsewhere?
Found it -
nano /etc/xdg/openbox/rc.xml
Thanks.
Last edited by truelinux (2025-08-08 09:30:51)
Offline
Since my BL Boron install I've been switching between my 4 workspaces using the mouse. But aren't there also preset keybindings available for this?
I've looked in: ~/.config/openbox/rc.xml. and ~/.config/openbox/bl-rc.xml. and they're both empty. I figured I could create my own but unsure how and if that should be done in one of the above config files or elsewhere?
Found it -
nano /etc/xdg/openbox/rc.xml
That's not a normal system.
Both ~/.config/openbox/rc.xml. and ~/.config/openbox/bl-rc.xml should exist, and certainly on a BL system ~/.config/openbox/bl-rc.xml is the file where settings are made. If those files exist openbox should ignore /etc/xdg/openbox/rc.xml although many settings are identical.
Another file where app keybinds are set is ~/.xbindkeysrc
On a Bunsenlabs system you can see all your keybindings from the menu > User Settings > Keybinds
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I am still learning this, so likely have things incorrectly set after my attempts - thanks for your patience.
The config file at /etc/xdg/openbox/rc.xml tells me not to edit there, but to create a new config file in my home dir - so whether this config file is the one used or not, I did do that:
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/rc.xml
Both ~/.config/openbox/rc.xml. and ~/.config/openbox/bl-rc.xml DO exist as you say they should. And for Boron it appears that bl-rc.xml that is the config file being used as expected --
ben@boron:~$ ps aux | grep openbox | grep -- --config-file
ben 1320 0.0 0.1 298456 21980 ? Ss 04:39 0:03 /usr/bin/openbox --config-file /home/ben/.config/openbox/bl-rc.xml --startup /usr/lib/bunsen/configs/bunsen-autostart
I'd like to set things up properly but need to understand which of these config files the system's actually using.
Also, this began because I'm trying to switch away from mouse and use keys when possible, so I was attempting to create a keybinding where I can 'jump' to tint panel from active window. For ex. - I'm typing here in forum window on Firefox and want to jump to my open terminal (X-Terminal-emulator) with keys instead of mouse. I tried both methods below. I used Superkey and P (for panel), then openbox --reconfigure, but it didn't work.
(xprop confirmed that class is 'Tint2' for panel, and 'X-Terminal-emulator' for terminal.)
<keybind key="W-p"> <!-- Or any unused key combo -->
<action name="Focus">
<class>Tint2</class> <!-- Match CASE from xprop! -->
</action>
<action name="Raise"/> <!-- Optional: bring panel forward -->
</keybind>
283 <keybind key="W-p">
284 <action name="Execute">
285 <command>wmctrl -x -a Tint2</command> <!-- -x matches class -->
286 </action>
287 </keybind>
I run Boron on all my computers and use no other OS. I'm a retired engineering tech and Linux enthusiast with a bit too much free time and I love to configure. I'm definitely respectful of those on this forum who may have actual work to do. So - thanks for any help!
Last edited by truelinux (2025-08-08 11:43:04)
Offline
I think tint2 is coded to not accept focus like that.
In the xprop output for tint2 you should see something like:
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK
WM_HINTS(WM_HINTS):
Client accepts input or input focus: False <--- I think that is the one that matters
If tint2 (any dock/panel) accepted focus like a normal window, they would show up in the list when cycling windows with ALT-TAB (or whatever binding is set to cycle windows).
For comparison in thunar (xterm is similar) the xprop output is:
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
You must unlearn what you have learned.
-- yoda
Offline
Thanks for that. After using xprop command I can see you're correct - tint2 panel is indeed set to false, so not possible. Fortunately, though I can't do what I wanted, I learned a lot by trying. Your response helped a LOT, pointing me directly to the issue so I could see and understand for myself.
I'm always aiming to stop going from the keyboard to that damn mouse, but it's just how it is. Still, I like openbox better than any desktop environment and so do my machines, which is why I use it. Thanks again!
Ben
"Machines just got workings and they talk to me.” - Kaylee Frye (Firefly)
Last edited by truelinux (2025-08-08 14:36:16)
Offline