zsh-workers
 help / color / mirror / code / Atom feed
From: Alan Orth <alan.orth@gmail.com>
To: zsh-workers@zsh.org
Subject: rsync completions
Date: Thu, 18 Aug 2022 11:07:12 -0700	[thread overview]
Message-ID: <CAKKdN4UaNAmTHwo7Ut__PcEUCevnBiaWVNGZCoXELn43Q93V1Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

Dear zsh-workers,

A few months ago the zsh completions for rsync stopped working correctly.
Tab completion of remote paths currently triple escapes special characters,
for example:

$ rsync -av 1.2.3.4:/home/me/downloads/Some\\\ File\\\ With\\\ Spaces ~/

This now results in an error, ie:

rsync: link_stat "/home/me/downloads/Some\ File\ With\ Spaces" failed:
No such file or directory (2)

I have to manually correct the triple escapes to use a single escape like
this for it to work:

$ rsync -av 1.2.3.4:/home/me/downloads/Some\ File\ With\ Spaces ~/

After some research I found that rsync 3.2.4 introduced changes to argument
parsing behavior¹ on 2022-04-15. This was patched by the fish shell²
recently shortly after the rsync 3.2.4 release.

Apologies if the zsh-workers is not the correct place to post this. I would
appreciate any advice or assistance on this, for example if it's a
distribution issue I will gladly file an issue elsewhere. I'm on Arch Linux
with zsh 5.9 and rsync 3.2.5.

Thank you!

¹ https://download.samba.org/pub/rsync/NEWS#3.2.4
² https://github.com/fish-shell/fish-shell/issues/8895

-- 
Alan Orth
alan.orth@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch

[-- Attachment #2: Type: text/html, Size: 2024 bytes --]

             reply	other threads:[~2022-08-18 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 18:07 Alan Orth [this message]
2022-08-18 23:57 ` Bart Schaefer
2022-08-19  2:26   ` Mikael Magnusson
2022-08-20 20:29     ` Alan Orth

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=CAKKdN4UaNAmTHwo7Ut__PcEUCevnBiaWVNGZCoXELn43Q93V1Q@mail.gmail.com \
    --to=alan.orth@gmail.com \
    --cc=zsh-workers@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).