zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>,
	"'Zsh hackers list'" <zsh-workers@sunsite.dk>
Subject: Re: _call_program (and possibly other hooks) or opt_args quoting prob lem.
Date: Fri, 17 May 2002 18:39:16 +0000	[thread overview]
Message-ID: <1020517183916.ZM20203@candle.brasslantern.com> (raw)
In-Reply-To: <6134254DE87BD411908B00A0C99B044F0369C2F3@mowd019a.mow.siemens.ru>

On May 16,  8:32pm, Borsenkow Andrej wrote:
}
} _call_program evals its argument(s). It creates very interesting problem -
} we want to quote word separator _but_ we do not want to quote possible
} parameter expansions ...

What about this?

Index: Completion/Base/Utility/_call_program
===================================================================
retrieving revision 1.1.1.1
diff -c -r1.1.1.1 _call_program
--- Completion/Base/Utility/_call_program	2001/04/09 20:14:08	1.1.1.1
+++ Completion/Base/Utility/_call_program	2002/05/17 18:38:04
@@ -4,7 +4,7 @@
 
 if zstyle -s ":completion:${curcontext}:${1}" command tmp; then
   if [[ "$tmp" = -* ]]; then
-    eval "$tmp[2,-1]" "$argv[2,-1]"
+    eval "$tmp[2,-1]" "${(qqq)argv[2,-1]}"
   else
     eval "$tmp"
   fi



-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2002-05-17 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 16:32 Borsenkow Andrej
2002-05-17 18:39 ` Bart Schaefer [this message]
2002-05-18 11:24   ` Borsenkow Andrej
2002-05-20 16:40     ` Bart Schaefer
2002-05-20 17:43       ` Borsenkow Andrej
2002-05-21  8:14         ` Sven Wischnowsky
2002-05-21 16:17           ` Bart Schaefer
2002-05-23 12:20             ` Sven Wischnowsky

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=1020517183916.ZM20203@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --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).