Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Problem with completion matching control
- X-seq: zsh-workers 5493
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: Problem with completion matching control
- Date: Tue, 23 Feb 1999 21:11:24 -0800 (PST)
- Cc: zsh-workers@xxxxxxxxxxxxxx
- In-reply-to: <199902231004.LAA24080@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199902231004.LAA24080@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: Bart Schaefer <schaefer@xxxxxxxxxxx>
Sven Wischnowsky writes:
>
> +/* This says what of the state the line is in when completion is started *
> + * came from a previous completion. If the FC_LINE bit is set, the *
> + * string was inserted. If FC_INWORD is set, the last completion moved *
> + * the cursor into the word although it was at the end of it when the *
> + * last completion was invoked. *
> + * This is used to detect if the string should be taken as an exact *
> + * match (see do_ambiguous()) and if the cursor has to be moved to the *
> + * end of the word before generating the completions. */
Is that really good enough? Can't the cursor sometimes move from one
place in the middle of a word, to some other place in the middle of
the same word, depending on exactly what matches are generated?
Particularly in the case (ahem) of a case-insensitive matcher?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author