You are not logged in.
this was a pretty awesome OOTB setup
Thanks!
I will actually use this desktop (unlike openbox) so I should hopefully be able to add some more polish as we go.
Offline
For my part, I'm really happy with Openbox. I never needed or missed a start menu. Openbox distinguishes itself by the fact that you can right-click your menu anytime and anywhere. It's possible that other window managers also have their strengths and may be more modern, but #! and now BL are Openbox distributions. In my opinion, the combination of Openbox+Tint2+Conky is simply outstanding. If you want more, you have to install it yourself. Maybe BL will be able to offer so-called meta-packages at some point, where you can retrofit another WM or add additional functions.
Cheers!
Offline
For my part, I'm really happy with Openbox. I never needed or missed a start menu. Openbox distinguishes itself by the fact that you can right-click your menu anytime and anywhere. It's possible that other window managers also have their strengths and may be more modern, but #! and now BL are Openbox distributions. In my opinion, the combination of Openbox+Tint2+Conky is simply outstanding. If you want more, you have to install it yourself. ....
Cheers!
Yes, I could not agree more.
Offline
Maybe BL will be able to offer so-called meta-packages at some point, where you can retrofit another WM or add additional functions
Well I could certainly create a package that would install the necessary files but the problem with our desktop is that any configuration is done at the user level and APT won't touch files in $HOME so any putative package would have to be installed before the first login (ie, during the installation process) for it to work seamlessly. If the package was installed afterwards then the configuration files would have to be copied over manually (as outlined in the OP).
My suggestion really does just amount to three added packages (plus libraries at ~1MiB extra added size in total) and two configuration files for an entire extra desktop that offers something not currently available in any other distribution — I thought that this was a good idea but clearly the community disagrees
Offline
I don't disagree at all! I am very appreciative that you put together and shared this. I don't understand the reactions.
Offline
thoro wrote:Maybe BL will be able to offer so-called meta-packages at some point, where you can retrofit another WM or add additional functions
Well I could certainly create a package that would install the necessary files but the problem with our desktop is that any configuration is done at the user level and APT won't touch files in $HOME...
A couple of suggestions:
1) Install the necessary user config files somewhere under /usr/share and also ship a script /usr/bin/install_bspwm_config which copies what's needed into $HOME. Users would need to run that script once after installing the package.
2) A bit snazzier: install /usr/share/xsessions/bspwm_session.desktop, whose Exec command runs /usr/lib/bspwm_startup, which does some tests and copies those config files into $HOME if they don't yet exist, does any other stuff that would be better done here than in the user's ~/.config/bspwm/bspwm, and then runs whatever /usr/share/xsessions/bspwm.desktop does.
...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
A bit snazzier: install /usr/share/xsessions/bspwm_session.desktop, whose Exec command runs /usr/lib/bspwm_startup, which does some tests and copies those config files into $HOME if they don't yet exist, does any other stuff that would be better done here than in the user's ~/.config/bspwm/bspwm, and then runs whatever /usr/share/xsessions/bspwm.desktop does.
^ I like this idea very much, thanks!
Offline
Thanks for the heads-up but I can't reproduce that in my test system, were you using LightDM when you experienced those issues?
May have been originally; I use lxdm now so might be an issue with that.
Once the new bl-exit code is finalised I will fork it and attempt to apply a conditional test (or something) so that it works in both, that would be my preference.
If you're going to fork the script, why not go with a more generic command; this command:
killall `wmctrl -m | awk '/Name/ {print tolower($2)}'`
shoudl log you out of 99% of the window managers (Doesn't work with xmonad, probably some other exotic ones).
Unless you're looking to sharpen your ninja scripting skills, then good luck with it.
I have added support for logging out of bspwm in the newest bunsen-exit that I have been working on. I also added the above script but have not yet confirmed that it will actually work. I should have the new bunsen-exit alpha ready before too much longer.
Offline
I realize this thread is a bit old, but I wasn’t aware that HoaS was working on bspwm in BunsenLabs as a sort of side project. I don’t know how much interest other community members have shown (perhaps outside of the forums if not inside), but I for one would like to see a bspwm edition of BunsenLabs as an alternative offering!
Last edited by nobody5 (2018-06-02 20:23:59)
Offline
I realize this thread is a bit old, but I wasn’t aware that HoaS was working on bspwm in BunsenLabs as a sort of side project. I don’t know how much interest other community members have shown (perhaps outside of the forums if not inside), but I for one would like to see a bspwm edition of BunsenLabs as an alternative offering!
This does sound interesting and this could be the framework for adding other WM's to BL. By just installing a metapackage then setting up a new WM such as bspwm should be a breeze with say a postinst script setting up a sensible default config to match BL.
Or what about this being a part of bl-welcome, perhaps part of a misc setup option?
Real Men Use Linux
Offline
I wasn’t aware that HoaS was working on bspwm in BunsenLabs
Working hard or hardly working? :8
I'm afraid it has been the latter recently, I was somewhat distracted by the Helium release and more recently production grade 3D rendering (don't ask); my interests are always peripatetic.
By just installing a metapackage then setting up a new WM such as bspwm should be a breeze with say a postinst script setting up a sensible default config to match BL.
Yes, good idea, I will look into that — a package based solution could be generalised to all Debian systems, which would be nice.
EDIT: in the meantime, the good folks over at ArchLabs have a bspwm desktop option available
Last edited by Head_on_a_Stick (2018-06-03 08:32:47)
Offline
I read just yesterday how light bspwm is. I'm just now getting use to i3. bspwm seems even stranger, by its looks only, one coming from the GUI world.
I would be interested in users actually using bspwm; thoughts, conclusions.
Offline
Some info links...
https://wiki.archlinux.org/index.php/Bspwm
https://github.com/windelicato/dotfiles … or-dummies
https://github.com/baskerville/bspwm
https://www.youtube.com/watch?v=_pA6EaUkep0
I don't care what you do at home. Would you care to explain?
Offline
As DeepDayze has stated, it would be great if we could get bspwm as a metapackage or something that can be installed and offered pre-configured via the bl-welcome script. And no worries, HoaS! But the work you have shared with the community thus far regarding bspwm does look very promising. It would be so awesome to see it offered via bl-welcome with a default set-up that is nearly identical to BL Openbox (as far as the bar, color scheme and conky are concerned). And thanks for sharing about ArchLabs and thank you hhh for those links!
Offline