> Hi Norman, > > On Thu, Nov 27, 2008 at 15:09:03 -0500, Norman Ramsey wrote: > > I use darcs w -sl as a regular part of my workflow. > > It would speed things up enormously if I could tell darcs > > on the command line that certain files are boring. > > > > E.g., > > > > darcs addboring empty umasm echo.txt > > Would the boring file mechanism work well enough for you?
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, but you're also imposing on me the additional cognitive burden of translating a file name to a regular expression matching that file name and *only* that file name (God help me should I forget to escape a dot). I understand the power of regexps for detecting boringness, but there's a reason the shell uses globbing patterns and not regexps. For the human interface, regexps are a tool of the devil. > You can edit _darcs/prefs/boring or perhaps write a script to do > that for you. I can't write a reliable script because darcs has no 'getpref' so I can't easily discover the identity of the boringfile my script should be editing. Norman _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
