From: Wayne Davison <wayned@users.sourceforge.net>
To: zsh-workers@sunsite.dk
Subject: characters not added in _rsync completion
Date: Tue, 12 Oct 2004 22:40:15 -0700 [thread overview]
Message-ID: <20041013054015.GA824@blorf.net> (raw)
I've noticed something strange in the _rsync completion in 4.2.1 (I
tested both the debian packaged version of 4.2.1 and the latest CVS):
zsh sometimes fails to add all the common characters that it should
when completing an ambiguous option. For example:
zsh -f
autoload -U compinit
compinit
rsync --bl<TAB>
The characters "ock" should be added (since the "--block" prefix is
common to both the listed completions), but nothing is added (the user
must either type more characters to remove the ambiguity, or cycle
through the matches with more TAB presses).
Other completions that fail to add common characters:
rsync --ch<TAB> # should add "ecksum"
rsync --com<TAB> # should add "p"
rsync --li<TAB> # should add "nk"
rsync --no<TAB> # should add "-"
rsync --par<TAB> # should add "tial"
rsync --ti<TAB> # should add "me"
(Note that two of those require a very recent rsync that has the
--checksum-seed and --partial-dir options, otherwise there would
be only one option to complete.)
However, most other options behave in the expected manner:
rsync --ba<TAB> # adds "ckup"
rsync --del<TAB> # adds "ete"
rsync --exc<TAB> # adds "lude"
rsync --ig<TAB> # adds "nore-"
rsync --inc<TAB> # adds "lude"
rsync --v<TAB> # adds "er"
Would anyone care to look into this?
..wayne..
next reply other threads:[~2004-10-13 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 5:40 Wayne Davison [this message]
2004-10-13 6:41 ` Bart Schaefer
2004-10-13 16:17 ` Clint Adams
2004-10-13 16:46 ` Wayne Davison
2004-10-13 17:03 ` Wayne Davison
2004-10-15 4:18 ` Bart Schaefer
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=20041013054015.GA824@blorf.net \
--to=wayned@users.sourceforge.net \
--cc=zsh-workers@sunsite.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).