[darcs-users] user interface wish list

[Peter Maxwell]

On Monday, October 6, 2003, at 10:37 PM, David Roundy wrote:
> I agree that this is a pretty terrible interface, but my plan is 
> rather to
> replace it (leaving the old interface as an option, of course)

Even so, it would be nice to see its few remaining flaws (over the ones 
inherent in its question-and-answer style) fixed one day, because there 
aren't many left (I count only 3:  (b)ack, silently accepting invalid 
input as 'n', silently accepting invalid options), it will be the only 
interface for a little while yet, and, as you say, it will remain an 
option for longer.

> that prompt with 'y' or 'n', and if you answer 'y', then it should 
> pull up
> an editor in which you can enter the long prompt.  Is this not what 
> happens
> for you?

Um, yes.  And the moral of the story is check and double check before 
posting bug reports.

> Done.
> Done.

Thanks!

> I have added a prefs file _darcs/prefs/author, and the first time you
> record (if $DARCS_EMAIL and $EMAIL aren't defined) I prompt for the
> address, and give a note where it will be stored so the user will know
> where to change it.

Great.  That was my favorite solution, but I thought I'd ask for 
something simpler.

>> argues that symlinks and file permissions are not "source", and are 
>> the
>> business of the build system rather than the RCS.   I agree they
>> shouldn't be mistaken for regular files though - how about if for now
>> they are just ignored?
>
> Sure.  Any idea how to do so?

I don't know enough Haskell to test it, but from its name I would hope 
that the function isRegularFile, in the Posix module, distinguishes 
between symlinks and regular files.  I imagine that isRegularFile and 
isDirectory could be used as part of determining the "boring"ness of 
the file name.  Any path that is neither a directory nor a regular file 
could be treated just like a boring file.

  -- Peter