zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: "Jun. T" <takimoto-j@kba.biglobe.ne.jp>
Cc: zsh-workers@zsh.org
Subject: Re: How about separating "_arguments --" into a new function?
Date: Mon, 25 Oct 2021 19:46:51 +0000	[thread overview]
Message-ID: <20211025194651.GC8612@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <19B5D2FE-1409-4B6C-A89A-F8DCEE9DF69A@kba.biglobe.ne.jp>

Jun. T wrote on Sun, Oct 24, 2021 at 18:53:52 +0900:
> 
> > 2021/10/21 23:15, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> 
> > The content
> > of ${_args_cache_foo} need to be escaped once for their transit through
> > lex.c when _foo will be read by compinit, and once against «echo»'s
> > treatment of backslashes.
> 
> I know.
> But if the output of 'cmd --help' already has '\', for example
>     --escape     replace $ by \$
> then 'print -r' does not work either (if the output of 'print -r' is used
> as a spec for _arguments as is).

The output of `print -r` should not be used as an _arguments spec as-is;
backslashes, colons, and square brackets need to be escaped.

> Using (qq) (instead of (qqq)) may or may not help, but then users must
> unset RC_QUOTE (before calling print/echo).
> But anyway $_args_cache_cmd is just a 'draft' of _cmd, and users
> must edit it manually (usually lots of editing are required).
> 
> I'll push the following soon, so feel free to modify/improve it.
> 

LGTM.

Thanks,

Daniel


      reply	other threads:[~2021-10-25 19:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 16:12 Jun. T
2021-10-12 16:04 ` Daniel Shahaf
2021-10-14 10:58   ` Jun T
2021-10-17 16:49     ` Daniel Shahaf
2021-10-18  4:40       ` Jun T
2021-10-21 14:15         ` Daniel Shahaf
2021-10-24  9:53           ` Jun. T
2021-10-25 19:46             ` Daniel Shahaf [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=20211025194651.GC8612@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --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).