From: Yuri D'Elia <wavexx@thregr.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: rsync --progress stops completion
Date: Wed, 17 Sep 2014 10:08:56 +0200 [thread overview]
Message-ID: <54194198.2010607@thregr.org> (raw)
In-Reply-To: <140916175124.ZM5742@torch.brasslantern.com>
On 09/17/2014 02:51 AM, Bart Schaefer wrote:
> (Wow, gmane sent Yuri's messaeg through with no To/Cc headers.)
[I bcc'ed you]
> Whoever most recently updated the _arguments call in _rsync asserted that
> -P and --progress are mutually exclusive. That's intended to prevent the
> --progress option from being offered again if you already used -P, I'm
> sure, but it also means that the comparguments builtin treats them as
> truly mutually exclusive, i.e., the command is wrong if both appear.
>
> Currently _rsync also excludes -P when either of --progress or --partial
> already appears, which is probably a mistake.
However, I'm wondering if we can make completion continue.
It happens to me from time to time, though I'm usually not motivated
enough to report it, that a command which is perfectly fine does not
perform file completion anymore, which is probably *the* most important
completer I care about.
Is there a way to somehow get this as a general behavior, or it's
dependent on the specific command completion? I'd rather have an error
spew from the command itself, than trying to figure out that I specified
a wrong flag and thus I cannot complete anymore.
It happens to me enough that I have bound key to force file completion:
bindkey -M emacs "^x^f" complete-files
I "shouldn't" need it though, in theory.
next prev parent reply other threads:[~2014-09-17 8:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 15:00 Yuri D'Elia
2014-09-16 15:09 ` Vadim A. Misbakh-Soloviov
2014-09-16 17:50 ` Yuri D'Elia
2014-09-17 0:51 ` Bart Schaefer
2014-09-17 8:08 ` Yuri D'Elia [this message]
2014-09-17 15:51 ` Bart Schaefer
2014-09-18 9:42 ` Yuri D'Elia
2014-09-18 16:36 ` Bart Schaefer
2014-09-19 2:01 ` Bart Schaefer
2014-09-19 3:22 ` Mikael Magnusson
2014-09-19 11:40 ` Oliver Kiddle
2014-09-21 0:48 ` Bart Schaefer
2014-09-20 13:25 ` Yuri D'Elia
2014-09-20 18:20 ` Bart Schaefer
2014-09-21 16:43 ` Yuri D'Elia
2014-09-21 17:20 ` Bart Schaefer
2014-09-21 17:33 ` Yuri D'Elia
2014-09-21 19:38 ` Bart Schaefer
2014-09-21 20:27 ` Yuri D'Elia
2014-09-21 20:37 ` Yuri D'Elia
2014-09-21 22:07 ` Bart Schaefer
2014-09-21 22:29 ` Yuri D'Elia
2014-09-22 6:58 ` Bart Schaefer
2014-09-21 21:08 ` Bart Schaefer
2014-09-21 21:35 ` Yuri D'Elia
2014-09-21 21:54 ` typeset -g (was Re: rsync --progress stops completion) Bart Schaefer
2014-09-21 18:52 ` rsync --progress stops completion Yuri D'Elia
2014-09-21 18:59 ` Yuri D'Elia
2014-09-20 13:20 ` Yuri D'Elia
2014-09-23 14:23 ` Oliver Kiddle
2014-09-23 14:43 ` Peter Stephenson
2014-09-16 15:25 ` Vadim A. Misbakh-Soloviov
2014-09-16 16:28 ` 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=54194198.2010607@thregr.org \
--to=wavexx@thregr.org \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/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).