I think that tab completion should only modify the command line if there is
a single possible change. This is consistent with other tab completions...
when you type linux<tab> in your source directory, it does not tab-complete
to the first result, it lists the possible alternatives (all the kernel
sources you have installed).
The only difference with wildcards is that you are choosing between
different modifications of the input string. Perhaps the completion list
should look something like this:
linux> rm ab*<tab>
Ab* Absolute.txt, Abstract.txt, Abrasive.txt...
aB* aBumblebee.txt, aBrat.txt, aBook.txt...
linux> rm ab*
The user will need to modify the input string themselves, just like they
have to now when completing a file. But if there is only one possible
case-insensitive match, then the input string should be altered to match
when they hit tab, the possible results listed, and the altered characters
highlighted:
linux> rm ab*<tab>
Ab* Absolute.txt, Abstract.txt, Abrasive.txt...
linux> rm Ab*
Is that consistent enough with existing practices?
On 3/1/07, Philip Ganchev <[EMAIL PROTECTED]> wrote:
On 3/1/07, Martin Bähr <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 02, 2007 at 01:04:54AM +0200, Beni Cherniavsky wrote:
> > In cases when there is no single completion that will cover all cases,
> > I as a user would expect the competing options (e.g. '*AB*cd' and
> > '*ab*cd') to be presented as alternative completions.
If there were no wildcards, wouldn't there be the same problem? That
is, if "Ab" and "aB" are both correct tokens, and you try to complete
"ab". I would expect it not to be changed, as there is more than one
possible completion. Only change the token if there is just one
possible completion. I think that covers all cases, no?
> even if there is only a single completion, it should still be presented
> as a choice (between failing to complete and changing case)
>
> automaticly changing case can be harmful if it is unnoticed in
> situations where i eg want to remove files that have one case and keep
> the ones with the other. if there are no files to be removed then the
> case change could potentially cause me to remove the ones i want to
> keep.
>
> maybe overriding the case should only be actively invoked somehow...
You could use the same key (Tab) to get to each next option as you do
to bring up the options. hit Tab once to see the completions and
again to iterate through them. But I think it is better to complete
it automatically and predictably in a way usually correct, and provide
a way to easily undo the change. Undo is needed in general.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
