upgrade & bar config

[mariusrugan]

hi,

first of all, nice work , thanks for all the time you've put in! i'm using orw on a debian based distro (kali) on a older macbook air under a test user.

i've pulled latest master and ran into some "issues" so please accept them as bulk under a wrong title :)

1. i've pulled latest master and i thought i ran ./setup.sh again and everything that i've customised (bar config) was overwritten, and the backup of home dir seems to be corrupted (not a gzip only tar, i've tried tar -xzpf); i'll look also into that but what is strange is there is a .git being copied in the .orw files in $HOME.

So the issue(s) - can you think please of writing some simple upgrade steps ? also - backup archive creation has to follow symlinks but transform them in hardlinks. (https://unix.stackexchange.com/questions/32633/how-to-create-backup-from-symbolic-links) - didn't look at all yet at that script could be that i am wrong but i've seen symlinks inside.

2. i've dug into the configuration & scripts being executed and i found the bar generation (lemonbar) and i've found the 2 bars that are generated, can you please help with some docs? e.g. bars in use are: ~/.config/orw/bar/configs/mid and ...

3. mpd_notifier is clogging a some of my CPU (16% in htop), and i don't know where to start looking for disabling it. can you please help ?

thanks!

[s0la]

Hi!

Thanks for giving ORW a shot, and thanks for pointing out this issues, I really appreciate it! :)

Ok, so, first issue:

When you want to upgrade, I think simple git pull would be enought (didn't test it, though, since I always have latest version on my development machine), but, hypothetically, it should be all you need, since changes are usually being made in scripts directory, or in dotfiles, so there is no need to run setup after pull.. Setup is used only if ORW is not installed at all, to place all files, link them, backup existing configs, and install necessary applications :)

As for symlinks, I'll definitely look that up, and thanks a lot for already providing source to the solution.. I will also test whole backup machanism after adding flag in question, so I'll keep you posted..

Regarding the second issue, you can use barctl command to manage bars, like this: barctl.sh -b <BAR_NAME> -k

Where is name of the bar you want to affect (list of comma-separated names is also supported), and k flag is for closing them :) In your case, it would be: barctl.sh -b mid,.. -k and to run bars you actually want to keep, do the same just without k flag, like this: barctl.sh -b full If "full" is name of bar config you'd like to run :)

I'm working on bar tutorial as we speak, so I'm sure all this will make much more sense when I release it :)

And, finally, you can disable mpd_notifier for running at boot by removing/commenting out corresponding line in ~/.config/openbox/autostart.sh, and to stop script imidiatelly, you can do it manually (by greping mpd_notifier from ps, and then kill its pid, which is second column), or simply run the following command: kill $(ps aux | awk '/mpd_notifier/ { print $2; exit }'), that should do the job! :)

Hope that help, and please sorry if I misunderstood some of your issues.. Please feel free to correct me and ask again! :)

[mariusrugan]

thanks for the detailed answer, i'll leave the issue open if that's ok with you so we can comment around the backup script, i don't mind testing around & provide some additional info if needed.

[s0la]

Glad that helped!

Ofc, that would be great! I'll let you know as soon as I fix backup! :)

[mariusrugan]

btw, off-topic,

take a look at bunsenlabs (crunchbang successor), they also do some nice openbox configs. https://www.bunsenlabs.org/img/frontpage-gallery/hydrogen2.jpg

EDIT: was thinking at how they use conky to display shortcuts

[s0la]

Thanks for the suggestion!! To be honest, I already thought of doing something similar, but maybe with rofi, instead of conky..

I'll definitelly consider it, thanks again! :)

[s0la]

Hey, sorry for not responding for such a long time, I was really busy past few day improving tiling capabilities..

Anyway, it seems like problem with backup was in directory path, since I usually run setup.sh from home directory, so, in my case, there was no need to explicitely specify home directory as the destination.. But, considering people can run it from any directory on the system, I explicitely specified home directory as argument for backup function, so now it should work as expacted :) I also added flag for storing actual files instead of links (big thanks for pointing that out!), so that should work as well :)

Btw, unrealated question, but this is quite unique oportunity, so I have to use it :D How does ORW perform on a macbook, and how is your experience with Linux in general on apple hardware?