nah bspwm always gotta be the superoir 
so what are we gonna fill these reops with commpile bspwm i the bspwm repo in one sxhkc in another and plynar i nthe last?
i s that that plan -and then we start on working on those configs
for the start yes
to who send repos?
Iām lready gtting ready for pushing sxhkd
but honestly before make it public, it would be better to make collaboration
it would be easer to mantain and to merge stuff
i made telegram group form this project
2 Likes
Thereās got to be an easier way to do this. I could put together a set up and people cold come with input what they want etc My gtthub skills are now officially on par with a 5 year young girl with no interest in computers.
1 Like
yes, this is true
1 Like
this is the easiest way.
gh give tools to team work
I get that - but it would be easier if one person just made a build of bspwm and then pushed it to GitHub where people could collaborate. Like now - I canāt even push to the repo cause I donāt have a user name and password. Say 4-5 ppl had equal access to the repo that would be an easier way to do it. so someone had an idea they could push it and everyone could see what was happening.
Iāve heard of this Github org where several people have equal acess I think that would be easier. Now itās just the two of us but also @xircon and @BONK have something to contribute to this
If not mistaken thatās how jaagr did it with polybar when he stopped working on it - he gave several persons equal access and it has worked out well. Maybe your daughter have some opinion on the matter?
I feel weāre kinda overcomplcate things- it just s simple build done in a few minutes. I could do that - and then the git wizards could do whatās needed on that end. Anyone whoās ever built bspwm know how minimal it is the config is 8 lines - the keybindings are longer ofc but is says something about how minmal this really is. I have some custom stuff in my bspwmrc and sxhkdrc - some scripts and external rules. but thatās things we want to leave out of a build like this. stay as close as defaults as possible would be my suggetsion. I remebmer some manjaro users on reddt were completely lost cuse they keybindings they were used to didnāt work on a default i3. so using defaults is a good thing IMHO
1 Like
btw Iāve used mech kb with no letters for the last time - itās even worse than autocorrect - I thought I would learn it pretty fast but I switch kbās too often. Have ordered a new now - with letters this time
so for anyone conidering buying a mechanical keyboard - do it - but have letterts on the keys - unless you 're gonna use only that one kb - then it will be a lot easier to get used to
1 Like
Ok peeps to simplified things.
I need to know who also will work with us
Then i can add them to telegram group ad to gh collaboration.
1 Like
yeah I think nano would be the right choice here as not everyone is comfortable with vim - or did you think something more like kate or whatever they are all called? I actually donāt know any but Kate I think but suggestions is always welcome 
I also thought of setting up mpd and ncmpcpp for them but many prefer gui music players but mpv for video should be ok
Micro is even easier than nano. Kate probably pulls a load of Plasma deps, featherpad is lighter:
l /usr/bin/featherpad
Permissions Size User Date Modified Name
.rwxr-xr-x 1.3M root 2020-07-05 13:37 /usr/bin/featherpad
Depends On : hunspell qt5-svg qt5-translations qt5-x11extras hicolor-icon-theme
I think vim with proppers config and easly accesable cheatsheet is better choise. Or maeby emacs? If youwant GUI text editor code-ossis better. Kate deppends on plasma.
youre ptobaby right about kate. minimal bspwm install and 2000 pkgs thx to kate
have never heard of the other two but as long as they are gui ppl should be satisfied
As think People who are interestednin wm are usualy tired of GUI. So minimal GUI apps will be best way i my opinion
1 Like