From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Infinite loop in parsing <()?
Date: Thu, 25 Mar 2010 07:21:54 -0700 [thread overview]
Message-ID: <100325072154.ZM26462@torch.brasslantern.com> (raw)
In-Reply-To: <20100325130601.1ad26f05@news01>
On Mar 25, 1:06pm, Peter Stephenson wrote:
}
} + print -u $ZTST_fd 'This test hangs the shell when it fails...'
} + alias sort='LC_ALL=C sort'
} + cat <(echo foo | sort)
} +0:Alias expansion works at the end of parsed strings
} +>foo
Probably not really anything to worry about, but this test will
fail without hanging if there is no "sort" command in the path.
next prev parent reply other threads:[~2010-03-25 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 18:22 Christian Neukirchen
2010-03-25 0:33 ` Bart Schaefer
2010-03-25 11:17 ` Christian Neukirchen
2010-03-25 13:06 ` Peter Stephenson
2010-03-25 14:21 ` Bart Schaefer [this message]
2010-03-25 15:16 ` Peter Stephenson
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=100325072154.ZM26462@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).