@alama
So that not to stray too far from the original question I looked into my Bunsenlabs Boron Openbox and I saw they use xbindkeys.
So tried in EOS yay xbindkeys
I don’t know how did you make LXQT Openbox usable- I simply ran
git clone https://github.com/EndeavourOS-Community-Editions/openbox.git
cd openbox
chmod +x openbox-install.sh
bash openbox-install.sh
then inserted into ~/.config/openbox/autostart xbindkeys -f $HOME/.xbindkeysrc
and created
/.xbindkeysrc
with content:
IDK why it had to be so complicated, but it works without touching the rc.xml.
BTW In LMDE 6 I used Boxes as VM for Archcraft as well. It works with the rc.xml way but do not want you to divert.
Interesting about xbindkeys. Xbindkeys may make sense for Bunsen Labs since they base their distro on openbox as a WM. Perhaps the xbindkey commands are less likely to get overwritten? My use scenario is a little different. I’m looking to openbox as an alternative/ backup WM so any commands specific to openbox I’d like to stay confined to openbox and not be system wide.
Openbox is installed as part of the lxqt package. It is used by LXQt as one of the choices in the session section of LXQt configuration center.
Logging into this Openbox just presents a cursor and blank screen. Right clicking will bring up the Openbox menu but none of the terminals referenced in the menu are installed by LXQt, and so possible there is nothing to do but exit. I have to follow suggestions from the Arch wiki from an LXQt session: cp -a /etc/xdg/openbox ~/.config/
Again within LXQt I edit Openbox’s menu.xml to make qterminal and pcmanfm-qt among others available. Then I can log into Openbox and take it from there.
I do have a question or two for you ESO. Why do you use git clone to install Openbox? I’ve never gone that route when I can just use pacman. Also, how can you update it that way?
I also learned some new facts since my last reply that put a hole in a couple of my theories. I helped a friend install Arch Linux on their computer and heard Ctl + Alt + F(n) works fine for them for changing the TTY. So my theory that possibly the arch install was missing something to enable this feature goes out the window now. Instead I have to focus on what I may have installed that is interfering.
Anyway, changing tty is not the most important thing since I can do it from the terminal if necessary. I have some questions about theming openbox that are more important for me and I will open a new thread to ask.
Or take it a step further and install the basic Openbox themes from the Archcraft repo or download them from GitHub. And in this way you get several really nice base themes to work with and modify to your heart’s content.