From: Bart Schaefer <schaefer@tiny.zanshin.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Problem with completion matching control
Date: Tue, 23 Feb 1999 21:11:24 -0800 (PST) [thread overview]
Message-ID: <14035.35324.873263.193885@c-bart.amazon.com> (raw)
In-Reply-To: <199902231004.LAA24080@beta.informatik.hu-berlin.de>
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?
next prev parent reply other threads:[~1999-02-24 5:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-23 10:04 Sven Wischnowsky
1999-02-24 5:11 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-24 8:39 Sven Wischnowsky
1999-02-22 23:35 Oliver Kiddle
1999-02-18 9:05 Sven Wischnowsky
1999-02-18 1:00 Oliver Kiddle
1999-02-17 8:00 Sven Wischnowsky
1999-02-16 13:58 Sven Wischnowsky
1999-02-16 17:04 ` Peter Stephenson
1999-02-16 8:30 Sven Wischnowsky
1999-02-16 1:14 Oliver Kiddle
1999-02-15 9:42 Sven Wischnowsky
1999-02-14 19:35 Oliver Kiddle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14035.35324.873263.193885@c-bart.amazon.com \
--to=schaefer@tiny.zanshin.com \
--cc=schaefer@zanshin.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).