Your best bet is probably using a modified WikiEngine. On 4/3/06, Ted Walther <[EMAIL PROTECTED]> wrote: > So I can hack it up? I'll need a listing of all changesets that touch a > particular line. And if I add lines, will that be tracked. Let's say I > want to view changes to Lk13:2, but I've added a couple verses to Jb42; > will annotate follow that change backward?
It would be much easier in darcs if you kept each verse in its own seperate file, as darcs' change management tools of this form (darcs changes, darcs mv) are really at the file/directory level. This would be a bit unusual perhaps, but you could create a very simple script to "cat" the entire work into that one monolithic file you are seeking, which becomes akin to the "compilation" stage of a program, and that you could even use ``darcs dist`` to run. You could even add the verse notations in that script and avoid having it stored redundantly in the "source" files. I'm not sure how happy you would be to work with such a structure like Luke\13\2.txt and Job\4\2.txt, though. > Also, because I want to run GNU wdiff, how do I do that? Maybe I'll > have to write my own thing simple software for this simple project. Right now darcs definitely does not support arbitrary diff-based patches (ie, patches for now will always be line-based). ``darcs diff``, for examing changes after the fact, could use alternate diff tools, but currently is hardwired to call ``diff``. You could override your path before calling darcs and and use a symlink diff -> wdiff. -- --Max Battcher-- http://www.worldmaker.net/ All progress is based upon a universal innate desire on the part of every organism to live beyond its income. --Samuel Butler _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
