You are not logged in.
https://raw.githubusercontent.com/Bunse … l-obthemes
BLOB now saves/restarts conkys which have been started on specific desktops. It also tests if OB, GTK and icon themes are still installed, before restoring: theme names are stored in 'settings.cfg' for display and reference.
There are a couple of bugfixes; and some changes to the format of 'settings.cfg', but I'm hoping it won't affect restoring old BLOB themes - testing needed!
Next thing might be to include tests for x-terminal-emulator, and have save options for configs (ATM we just handle Terminator). So if anyone has info about different terminal emulators, and where their configs are, it would save me a lot of experimenting
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
urxvt: ~/.Xresources
...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
First feedback:
Why does the BunsenLabs_Grey "blob" (what should we call these settings collections?) put a blue conky on the left, and have a blue tint2 to boot? My default Hydrogen BL never looked like that.
Could we have saved themes for bl-exit too? After switching to the BL grey look, the green exit box doesn't fit in.
EDIT: I now see that they are indeed being saved. Sorry (I was in a bit of a mess at first over ~/bin not being in $PATH...)
Anyway, it would be nice to be able to recreate the standard grey BL Hydrogen look for those who prefer it.
My mistake: in the latest bunsen-configs ~/.config/tint2/tint2rc-crunchbang{,-bottom} I overzealously changed the launcher icon theme to Paper. Of course for #! it should be Faenza-Bunsen. I'll fix that soon.
[With the Faenza-Bunsen icon theme, tint2's systray icons go black. This looks like a problem with Faenza-Bunsen, because it didn't work with QT5 apps either. Looks fine in Thunar though.]
EDIT: Not an issue - use Faenza-Bunsen-Dark for this dark desktop.
Last edited by johnraff (2017-09-11 03:22:50)
...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'll have a look tomorrow - too tired now after long shift with a million (nearly!) boats to organise through a lock
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
I'm in no rush, I plan on being around for a few years more.
Get some sleep, a million (nearly!) boats is a lot
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
WRT to other configs, my opinion would be to focus on graphics only - just visual appearance - else you'll end up trying to backup the whole desktop! Also, a lot of settings work equally well regardless of what theme/wallpaper/icons you're using.
...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
Bit more feedback:
Notice the start is now no longer the "Welcome" screen, but goes straight to the list of blobs. Is that what happens if there are some saved collections?
The missing icon theme check worked nicely. I would perhaps like an "Icon theme: " line (under "GTK theme: "?) in the confirmation message when saving or restoring. Would that be easy to add? EDIT: That was when restoring a blob saved by the previous script. Now it's there, just after GTK. Sorry for the confusion.
EDIT: Forgot to add, restoring blobs saved by the previous version of the script worked fine, apart from (reasonably) not showing the new information in the new script.
The login settings: saving /etc/lightdm/lightdm-gtk-greeter.conf will store the login theme, but if the login background is the default /etc/lightdm/lightdm-gtk-greeter.conf then that is a Debian alternative symlink which might have been changed by the admin, so the script will not know what image it points to. Since this is sysadmin stuff, might there be a case for just omitting it from BLOB and sticking exclusively to user settings? I realize a lot of users would want to tweak their login screen to match their desktop of course...
Last edited by johnraff (2017-09-11 03:20:47)
...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 tried tweaking the Helium-dev desktop to look as much like the "legacy" grey BL as possible, and saving the configs with the new BLOB. In case you thought it work bundling in bunsen-configs - or using as a basis for further tweaking - it's here: https://drive.google.com/file/d/0B7BNzo … sp=sharing
The dirname is 'john-legacy' because I was a bit hasty in choosing a name - bunsen-legacy or something would be better, probably meaning some search-and-replace in those files.
...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