On Fri, Feb 01, 2008 at 09:03:23AM +0100, Joerg van den Hoff wrote: > w.r.t. hacking it to your needs: it probably is nice that it's > "easy" to do so. but I'm conservative here: I believe in canonical > "offifical" releases (which might include of course the sensible > patches from the users). the same holds true here as it did above: > if I start (and am able) to mess with the source code, get some > desired functionality running (such as, e.g. the cycling through > tags), it will be gone with the next release and I have to start > thinking about putting my additions in a separate source file (or > lib), check that the function interfaces are unmodified in the next > release etc etc.
As I've been maintaining a patchset for a while[1], I can say that it
is quite painless to update the patches to a new dwm release.
E.g. the "everything into one file" release took only one afternoon of
work to update the patches - and that was one of the two biggest
upstream changes I can remember.
Regards,
Christian
[1] dwm-mitch
If you like the traditional workspace approach, have a look at it :-)
--
....Christian.Garbs.....................................http://www.cgarbs.de
_ _ _ _ _ _ __ news:de.alt.rec.ascii-art
\`../ |o_..__ \`../ |o_\`../ |o_..__ ___/ /__ ________ ________ _
`.,(_)______(_).> (_)_____'(_)______(_).> / _ / _ `/ __/ _ `/___/ _ `/
~jrei~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\_,_/\_,_/_/ \_,_/ \_,_/~~~~~
signature.asc
Description: Digital signature
