From: Martin Buchholz <martinrb@google.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org, Joel Ebel <jbebel@google.com>
Subject: Re: zsh ignores the arguments on its first command.
Date: Wed, 2 Jun 2010 00:05:20 -0700 [thread overview]
Message-ID: <AANLkTikvkgA0bFLLh7VLVtBbUVMdM64-2iQXjAVbHvaA@mail.gmail.com> (raw)
In-Reply-To: <201006012145.o51LjhGg005724@pws-pc.ntlworld.com>
On Tue, Jun 1, 2010 at 14:45, Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
> Martin Buchholz wrote:
> I think your terminal is being screwed up somehow. That explains both
> why you can't see the echo output and can't see the ${+terminfo}.
I expect ${+terminfo} to be 0, not to give an error.
> It usually helps if you can boil bugs down to what happens with the "-f"
> option, so we're not relying on unseen side effects of initialisation
> scripts.
Alright, let's try again to report the bug with the terminfo special
parameter and the zsh/terminfo module:
$ (unset TERM; zsh -fic 'echo $ZSH_VERSION; echo ${+terminfo}')
4.3.10
zsh:1: unknown parameter: terminfo
$ (unset TERM; zsh -fic 'echo $ZSH_VERSION; echo ${+terminfo}')
4.3.4
0
The behavior in 4.3.4 is the expected one,
and the behavior in 4.3.10 is a regression
introduced since then.
My guess is that the zsh core is not prepared to deal
with the NULL return from getterminfo.
Martin
next prev parent reply other threads:[~2010-06-02 7:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 21:23 Martin Buchholz
2010-06-01 21:45 ` Peter Stephenson
2010-06-01 22:27 ` Martin Buchholz
2010-06-02 7:05 ` Martin Buchholz [this message]
2010-06-02 11:19 ` Peter Stephenson
2010-06-02 16:44 ` Martin Buchholz
2010-06-03 9:01 ` Peter Stephenson
2010-06-03 13:22 ` Martin Buchholz
2010-06-03 13:32 ` Peter Stephenson
2010-06-03 13:47 ` Martin Buchholz
2010-06-03 14:15 ` Bart Schaefer
2010-06-03 14:20 ` 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=AANLkTikvkgA0bFLLh7VLVtBbUVMdM64-2iQXjAVbHvaA@mail.gmail.com \
--to=martinrb@google.com \
--cc=jbebel@google.com \
--cc=p.w.stephenson@ntlworld.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).