From: Wayne Davison <wayned@users.sourceforge.net>
To: zsh-workers@sunsite.dk
Subject: Re: characters not added in _rsync completion
Date: Wed, 13 Oct 2004 09:46:26 -0700 [thread overview]
Message-ID: <20041013164626.GA3017@blorf.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0410122330050.17741@toltec.zanshin.com>
On Tue, Oct 12, 2004 at 11:41:52PM -0700, Bart Schaefer wrote:
> I'm puzzled why the version of rsync itself makes any difference,
> because _rsync specifies everything explicitly, so unless you've
> edited _rsync it won't ever complete those options.
This is not how it works on my system. The _rsync script appears to be
querying rsync to ask it what options it supports, and combining that
list with the list in _rsync. So, if, for instance, you've installed
the rsync 2.6.3 package from debian unstable, the new options from all
the 2.6.x versions get listed, just without descriptions.
> Similarly, I have only --links and nothing else that matches --link.
Earlier rsyncs (prior to 2.6.0) didn't list --link-dest in their help
text, even when the option was supported (and our _rsync script was
missing this option as well -- I've fixed that in the latest CVS
version).
> Yet this one works for me:
> > rsync --no<TAB> # should add "-"
If I change rsync to 2.5.7 on my system, that one also begins to work.
However, with either a newer rsync (which lists --no-relative and
--no-implied-dirs in the help output) or if you edit the --no-relative
option into the _rsync script, it begins to fail.
> Without plunging into the why of it, a cursory inspection seems to
> indicate that when an option has an argument (e.g., --compa completes to
> --compare-dest= with the trailing equal sign) then zsh fails to find the
> longest common prefix among that option and any other options that do NOT
> have arguments (as --compress does not). All the cases that fail appear
> to have at least one option with, and at least one without, an argument.
It's strange that the --no<TAB> case doesn't match this idea.
..wayne..
next prev parent reply other threads:[~2004-10-13 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 5:40 Wayne Davison
2004-10-13 6:41 ` Bart Schaefer
2004-10-13 16:17 ` Clint Adams
2004-10-13 16:46 ` Wayne Davison [this message]
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=20041013164626.GA3017@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).