zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@berkom.de>
To: zsh-workers@sunsite.dk, Frank v Waveren <fvw@var.cx>
Subject: Re: zcompsys space character problem
Date: Wed, 6 Nov 2002 09:03:58 +0100	[thread overview]
Message-ID: <15816.52462.264530.186687@wischnow.berkom.de> (raw)
In-Reply-To: <1021105051003.ZM21024@candle.brasslantern.com>


Bart Schaefer wrote:

> ...
> 
> Changing line 461 from
> 
> 	compfiles -r tmp1 "$tmp3"
> 
> to
> 
> 	compfiles -r tmp1 "${(Q)tmp3}"
> 
> has the desired effect in this particular case, but I don't know if it is
> always correct.  Sven, are you out there?

I wasn't sure if it weren't better to put this into the C-code, but
leaving it in the shell code seems much more flexible (and, somehow,
logical).

Below is Bart's suggestion put into a patch which I'm goinh to commit.


Bye
  Sven

Index: Completion/Unix/Type/_path_files
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Type/_path_files,v
retrieving revision 1.19
diff -u -r1.19 _path_files
--- Completion/Unix/Type/_path_files	2 Jul 2002 14:06:49 -0000	1.19
+++ Completion/Unix/Type/_path_files	6 Nov 2002 07:55:34 -0000
@@ -464,7 +464,7 @@
     # names. This avoids having `foo' complete to `foo' and `foobar'.
     # The return value is non-zero if the component is ambiguous.
 
-    compfiles -r tmp1 "$tmp3"
+    compfiles -r tmp1 "${(Q)tmp3}"
     tmp4=$?
 
     if [[ "$tpre" = */* ]]; then

-- 
Sven Wischnowsky                          wischnow@berkom.de


      parent reply	other threads:[~2002-11-06  8:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  3:27 Frank v Waveren
2002-11-05  5:10 ` Bart Schaefer
2002-11-05 12:36   ` Sven Wischnowsky
2002-11-06  8:03   ` Sven Wischnowsky [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=15816.52462.264530.186687@wischnow.berkom.de \
    --to=wischnow@berkom.de \
    --cc=fvw@var.cx \
    --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).