Re: [dev] a few questions

2017-04-13 Thread Greg Reagle
On Thu, Apr 13, 2017, at 12:58, Greg Minshall wrote: > 3. i recently lost my ability to run X on my laptop, so lived with tmux > (which i heard about here, and very much like -- thanks!). this > experience emphasized that often i'd rather have a two-key (say) > sequence, ^B-j, rather than the "c

Re: [dev] a few questions

2017-04-13 Thread Inokentiy Babushkin
Hi, I am no developer of any of the suckless projects, but I guess I can outline how people I know, including myself, handle the configuration issue. > 1. when people make changes to their, e.g., config.def.h, how do they > deal with that w.r.t. git (branches, etc.)? i'd like to be able to use

Re: [dev] a few questions

2017-04-13 Thread Greg Reagle
Config.h is the file actually used to build the program. It is intended to be "manually" controlled by the user/developer, meaning not managed by git and not generated by a recipe in a makefile. It is for personal preferences. It is a sort of substitute for a .rc file. As far as i understand, y

[dev] a few questions

2017-04-13 Thread Greg Minshall
hi, all. thanks again for dwm, surf, both of which i use a lot. i had a few newbie questions. 1. when people make changes to their, e.g., config.def.h, how do they deal with that w.r.t. git (branches, etc.)? i'd like to be able to use git to track, but integrate my changes (without the danger