From: Klaus Ethgen <Klaus+zsh@Ethgen.ch>
To: zsh-workers@zsh.org
Subject: Re: Undocumented construct <<(
Date: Wed, 18 Nov 2015 16:00:03 +0100 [thread overview]
Message-ID: <20151118150003.GC10880@ikki.ethgen.ch> (raw)
In-Reply-To: <20151118144147.116022ee@pwslap01u.europe.root.pri>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Am Mi den 18. Nov 2015 um 15:41 schrieb Peter Stephenson:
> On Wed, 18 Nov 2015 15:23:08 +0100
> Klaus Ethgen <Klaus+zsh@Ethgen.ch> wrote:
> > I searched now pretty long for a undocumented construct <<(list).
>
> It's written confusingly (not the first time for a zsh construct :-/).
:-)
> It's particularly confusing given that "<<HERE" is indeed a special
> construct.
>
> What you're looking at is a normal < followed by a <(list),
Yes, that is the same. I just wasn't aware that it also work for the
special <(...) construct.
Nevertheless, thanks for the fast response and for documenting it.
For the records, I fixed zsh.vim to allow that syntactical sugar:
- --- /usr/share/vim/vim74/syntax/zsh.vim 2015-08-17 03:23:35.000000000 +0100
+++ zsh.vim 2015-11-18 15:44:37.885885225 +0100
@@ -55,7 +55,7 @@
syn match zshRedir '|&\='
syn region zshHereDoc matchgroup=zshRedir
- - \ start='<\@<!<<\s*\z([^<]\S*\)'
+ \ start='<\@<!<<\s*\z([^<(]\S*\)'
\ end='^\z1\>'
\ contains=@zshSubst
syn region zshHereDoc matchgroup=zshRedir
Maybe that can find a way into vim in some future time too. :-)
Regards
Klaus
- --
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <Klaus@Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQGcBAEBCgAGBQJWTJJtAAoJEKZ8CrGAGfasfvMMAKj1wrkbhqTgadiCrkoSmJdP
lI+oG48ccq5gmF7vNrOzWBJvBE4R1tFv/BqLyfjZXaRZzf9Yz3MDcLAdZgOzR3+K
wnN8RdO0WIt2iFClJME+XRhsgIlQ3UIn27WbWq0YgpGU7NHTOtJ0aDJBLTwSRgtN
N5bAVylQrX9BGjnVsgj+vJ2NbI1FiAFkLT38pk+vZA2JWKmqJb+YhdmfthOE/fxw
9tg+QF6YOKIYkKLMLjjRjSkA6s6iePiMr6dLMUMn04YjDKS88Aw7qKS3dJ020M1R
sqAg3tYUDWGU/peMCDUfVPo3mavn9TO640m7Q8A41XHskHW6tiZbl/jhorCF/idS
1W3YrBgY5RSPDF4cnslut+OCNrPBqckBhg80lMTrA+pGfAkgIWpxqSau7lWZ6gLj
hFl/BEgHIn1LoLW1ItfpMY0Jy9+sV/w73q1xyfcz8z0fIfZth9w42Ja7lx8IjQ9g
d9kXNUTkAw6/6ILHeAa7RKh2sEqgcqlbuooiHHEtRw==
=E+Mu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-18 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 14:23 Klaus Ethgen
2015-11-18 14:41 ` Peter Stephenson
2015-11-18 14:47 ` Peter Stephenson
2015-11-18 15:00 ` Klaus Ethgen [this message]
2015-11-18 22:55 ` Daniel Shahaf
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=20151118150003.GC10880@ikki.ethgen.ch \
--to=klaus+zsh@ethgen.ch \
--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).