From: Bart Schaefer <schaefer@brasslantern.com>
To: Wayne Davison <wayned@users.sourceforge.net>
Cc: zsh-workers@sunsite.dk
Subject: Re: characters not added in _rsync completion
Date: Thu, 14 Oct 2004 21:18:31 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0410131943440.24408@toltec.zanshin.com> (raw)
In-Reply-To: <20041013164626.GA3017@blorf.net>
On Wed, 13 Oct 2004, Wayne Davison wrote:
> 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.
I've belatedly spotted that _rsync does in fact pass the "--" option to
_arguments, which causes it to parse the --help output.
> > Without plunging into the why of it, a cursory inspection seems to
> > indicate that when an option has an argument then zsh fails to find
> > the longest common prefix among that option and any other options that
> > do NOT
>
> It's strange that the --no<TAB> case doesn't match this idea.
Hrm. Well, I did say it was a cursory inspection.
Fooling around with how this behaves in interactive menu selection is ...
unfortunately pretty much the opposite of "enlightening."
prev parent reply other threads:[~2004-10-15 4:19 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
2004-10-13 17:03 ` Wayne Davison
2004-10-15 4:18 ` Bart Schaefer [this message]
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=Pine.LNX.4.61.0410131943440.24408@toltec.zanshin.com \
--to=schaefer@brasslantern.com \
--cc=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).