[darcs-users] darcs feature request --- quick addition to boring file

[Trent W. Buck]

Norman Ramsey <nr at cs.tufts.edu> writes:

>>> Absolutely not.  Why should I interrupt a nice sensible command-line
>>> workflow to edit a boring file?  You're talking not only about
>>> expanding a 1-second task to *at* *least* 10 seconds or more just to
>>> fire up the editor and fool around,
>>
>> Who said anything about an editor?
>>
>>  >>_darcs/prefs/boring echo '^(./)?yow$'
>
> Not so easy.  If I'm working on GHC, it is almost certainly
> ../../_darcs or sometimes ../_darcs.  On other projects _darcs might
> work.  Do I want to keep track of the location of _darcs by hand?  I
> do not!  That's what tools are for.  And prefs/boring is not reliable
> either because somebody might have set the boringfile preference.

Well, the above works well enough for me when I occasionally want to
ignore patterns that are too dangerous to include in ~/.darcs/boring
(for example, ^(./)?doc/.*\.pdf$).  There are plenty of other things for
me to work on that I consider more important.

If it bothers you sufficiently, you can work on the code for this
yourself, or post a bounty for someone else to do so.  It won't
necessarily be accepted, but it'll be more productive (if less
cathartic) than ranting at the list :-)