zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: characters not added in _rsync completion
Date: Tue, 12 Oct 2004 23:41:52 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0410122330050.17741@toltec.zanshin.com> (raw)
In-Reply-To: <20041013054015.GA824@blorf.net>

On Tue, 12 Oct 2004, Wayne Davison wrote:

> zsh sometimes fails to add all the common characters that it should
> when completing an ambiguous option.
[...]
> (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.)

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.  Does Debian come with an updated 
_rsync for which a patch has not been posted back to zsh-workers?

Similarly, I have only --links and nothing else that matches --link.
However, I can reproduce this for several of the others that you list:

> rsync --com<TAB>   # should add "p"
> rsync --par<TAB>   # should add "tial"
> rsync --ti<TAB>    # should add "me"

Yet this one works for me:

> rsync --no<TAB>    # should add "-"

(That is, I do get "-" added when completing there.)

> Would anyone care to look into this?

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.


  reply	other threads:[~2004-10-13  6:42 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 [this message]
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=Pine.LNX.4.61.0410122330050.17741@toltec.zanshin.com \
    --to=schaefer@brasslantern.com \
    --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).