From: Bart Schaefer <firstname.lastname@example.org>
To: Alan Orth <email@example.com>
Subject: Re: rsync completions
Date: Thu, 18 Aug 2022 16:57:03 -0700 [thread overview]
Message-ID: <CAH+w=7bgJvySBm_s53Lw2mkNZbOwa_8k2UVZ2j6yyuQnERYFCg@mail.gmail.com> (raw)
On Thu, Aug 18, 2022 at 11:08 AM Alan Orth <firstname.lastname@example.org> wrote:
> A few months ago the zsh completions for rsync stopped working correctly.
So if this is a problem introduced by those quoting changes in rsync
3.2.x, then the rsync completion has to become version-aware, which I
see is what fish has done.
I'm not able to tell what ramifications this has when the remote
version differs significantly from the local version; it doesn't
appear fish is taking that into account, so perhaps it doesn't matter.
A quick workaround for you, Alan, is likely to be
alias rsync='rsync --old-args'
There might even be a clever way to insert --old-args into $BUFFER
only when completion has been invoked, but completion widgets don't
play well with "ordinary" line edits so I'm not going there just now.
next prev parent reply other threads:[~2022-08-18 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 18:07 Alan Orth
2022-08-18 23:57 ` Bart Schaefer [this message]
2022-08-19 2:26 ` Mikael Magnusson
2022-08-20 20:29 ` Alan Orth
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).