From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: _expand doesn't do brace expansion?
Date: Thu, 15 Jun 2000 10:22:22 +0000 [thread overview]
Message-ID: <1000615102222.ZM5037@candle.brasslantern.com> (raw)
In-Reply-To: <200006150920.LAA04751@beta.informatik.hu-berlin.de>
On Jun 15, 11:20am, Sven Wischnowsky wrote:
} Subject: Re: _expand doesn't do brace expansion?
}
} Oh, didn't everyone know that?
_complete manages to complete inside braces; why does the code that
understands braces stop taking them apart when there's a closed pair?
AFAICT, no completion works at all once any close brace is in place,
even if that's within an outer set of braces, e.g.
zagzig[52] ls Functions/({Mi<TAB>
zagzig[52] ls Functions/{{Misc/<,TAB>
zagzig[52] ls Functions/{{Misc,
Completing file
README.zftp Zftp/ Prompts/ CVS/
Makefile.in Zle/ Misc/
zagzig[52] ls Functions/{{Misc,P<TAB>
zagzig[52] ls Functions/{{Misc,Prompts/<},TAB>
zagzig[52] ls Functions/{{Misc,Prompts},
Completing `file' or `corrections'
(BEEP)
} % a='a{x,y}b'
} % echo ${(e)a}
} a{x,y}b
That is kinda grody.
It ought to be possible to turn 'a{x,y}b' into 'a${^=:-x y}b' and then
use ${(e)...} on that; but dang it's tough to match a curly brace inside
a ${var/pat/rep} expression without causing a parse error.
--
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
next prev parent reply other threads:[~2000-06-15 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 9:20 Sven Wischnowsky
2000-06-15 10:22 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-15 10:45 Sven Wischnowsky
2000-06-15 10:58 ` Sven Wischnowsky
2000-06-15 15:08 ` Bart Schaefer
2000-06-15 9:09 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=1000615102222.ZM5037@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).