From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: help with _match, globcomplete etc. (with a PATCH)
Date: Wed, 16 Feb 2000 10:57:55 +0000 [thread overview]
Message-ID: <1000216105755.ZM22565@candle.brasslantern.com> (raw)
In-Reply-To: <200002161011.LAA16009@beta.informatik.hu-berlin.de>
On Feb 16, 11:11am, Sven Wischnowsky wrote:
} Subject: Re: help with _match, globcomplete etc. (with a PATCH)
}
} Bart Schaefer wrote:
}
} > zsh% arr=('[sS]' Src/M ../)
} > zsh% print -l ${~^arr}*
} >
} > (I note that on that example expand-word produces a list of files but
} > the _expand completer (with substitute and glob styles set to 1) only
} > beeps, with or without 9752 applied. Is that the right behavior?)
}
} No. Seems like the (e) flag makes the thing be quoted as in double
} quotes. I.e. with a='${~^arr}*', ${(e)a} gives `[sS] Src/M ../*', but
} a='${(@)~^arr}' gives what we would have expected. The patch below
} changes the calls to parsestr() to calls to parse_subst_string() to
} get that. Hm, should we call that only conditionally, e.g. if the
} ${(e)...} is not inquotes and has no (@) or something?
My first reaction would be to answer "yes," and a little fooling around
with 9757 applied seems to bear it out:
a='*'
print -l "${(e)a}"
Would you really expect to get one file name per line in that case?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-02-16 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-16 10:11 Sven Wischnowsky
2000-02-16 10:57 ` Bart Schaefer [this message]
2000-02-16 11:18 ` Oliver Kiddle
-- strict thread matches above, loose matches on Subject: below --
2000-02-17 14:43 Sven Wischnowsky
2000-02-16 15:39 Sven Wischnowsky
2000-02-15 16:08 help with _match, globcomplete etc Sven Wischnowsky
2000-02-15 19:53 ` help with _match, globcomplete etc. (with a PATCH) Oliver Kiddle
2000-02-16 6:47 ` Bart Schaefer
2000-02-16 10:38 ` Oliver Kiddle
2000-02-16 11:52 ` Bart Schaefer
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=1000216105755.ZM22565@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).