[darcs-devel] [issue1946] nicer error message when "darcs changes" in not-a-repo
Eric Kow
bugs at darcs.net
Sat Sep 4 07:22:17 UTC 2010
Eric Kow <kowey at darcs.net> added the comment:
We should try to fix this sooner rather than later.
I suspect the problem is that darcs changes accepts --repo=URL (so you
can do something like darcs changes
--repo=http://repos.mornfall.net/hashed-storage) so it's not literally
true that you need to be in a repository to run this command.
So one view you could take is that we should use just the prerequisites
mechanism (implementor: copy from other commands), but with a phrasing
appropriate for --repo. What's a good phrasing?
Another view is that the prerequisite checker should fire two different
error messages depending on whether --repo is used or not. If repo is
not used (the more common case), it could say something like "You need
to either be in a repository or use the --repo flag to run this
command", and something else if --repo is supplied. Keep in mind that
--repo accepts both filepaths and URLs
----------
milestone: -> 2.8.0 HEAD
nosy: +jaredj
priority: -> feature
status: unknown -> need-implementation
topic: +ProbablyEasy, UI
__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue1946>
__________________________________
More information about the darcs-devel
mailing list