On Tue, Jul 24, 2007 at 09:12:55PM +0200, Eric Y. Kow wrote: > On Mon, Jul 23, 2007 at 22:33:56 +0200, Tommy Pettersson wrote: > > darcs changes --repo ../here :src/foo.c > > What's interesting about this idea is that it would provide an > unambiguous way to refer to a path; the user knows exactly what he is > going to get. > > That said, I'm not sure anybody would actually use it. Hmm...
Well, what I find somewhat of a problem is I can't use the normal basic shell completion. At present we use relative paths as repo paths. This was agreed to be the best solution some time back. It causes 'darcs changes --repo ../here ../here/foo.c' to NOT work, i.e., shell completion is rendered useless. And it gives us the other (this, issue405) problem: sorting out normal relative paths from repo relative paths on the command line. This happens, as I noted in another comment, not only for values to some flags, but also for arguments that are themselves paths to other repositories. So what I _really_ want is normal relative (and absolute) paths into different repos to work. But that's unfortunately impossible without supplying another way to type repo relative paths, or use AI, or some third option I haven't thought of. -- Tommy Pettersson <[EMAIL PROTECTED]> _______________________________________________ darcs-devel mailing list darcs-devel@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-devel
