Import of RT #214

David Roundy <droundy@abridgegame.org> 2005-02-09
-------------------------------------------------

On Wed, Feb 09, 2005 at 07:45:19PM +0200, Vassilii Khachaturov wrote:
> Here is a transcript:
>
> vassilii@ilmarinen:~$ darcs trackdown --he[TAB pressed]
> darcs failed: Can't run command trackdown here.
> You need to be in a repository directory to run this command.
> [output paused, ENTER pressed]

The problem here is that the bash completion calls darcs trackdown
--list-options to find out what flags exist, but this command fails because
darcs trackdown itself may only be run in a repository.

So the fix is to make --list-options able to run (as is the case with
--help) even when in a situation where the command itself cannot be run.
This isn't entirely trivial, since some features (e.g. completing for pull
using the repositories in _darcs/prefs/repos) won't work if you aren't in a
repository. Still, this shouldn't be *too* hard to fix.

Note that this is still an issue with darcs 1.0.8

Actually, maybe this should be a wont-fix.  I dunno.  In any case, it might not
be very easy to fix (see Darcs.Commands.run_command) because commands might need
to do their path-correction trickery in order for some of the completions to be
correct (I'm sort of guessing here).

Whoever looks into this might want to tread carefully.

Will-fix after all.  Resolved in unstable with the following patch.  Thanks!

Mon Jul 16 23:06:31 CEST 2007  Eric Kow <eric.kow@loria.fr>
  * Allow --list-options even if command cannot be run (issue297).
  
  If the command cannot be run, just print the possible flags, not the file args.