From: Clint Adams <clint@zsh.org>
To: "Murilo Opsfelder Araújo" <mopsfelder@gmail.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: zsh seg fault when TERM = linux
Date: Tue, 5 May 2009 15:40:16 +0000 [thread overview]
Message-ID: <20090505154016.GA19068@scru.org> (raw)
In-Reply-To: <e17dc37a0905040858t4886eb8bu53a297dc90f3eafe@mail.gmail.com>
On Mon, May 04, 2009 at 12:58:10PM -0300, Murilo Opsfelder Araújo wrote:
> ./config.h.in:#undef TGETENT_ACCEPTS_NULL
You need to run configure so that config.h will be generated. Then you
can check the setting there.
next prev parent reply other threads:[~2009-05-05 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 12:35 Murilo Opsfelder Araújo
2009-04-30 13:54 ` Peter Stephenson
2009-04-30 21:22 ` Murilo Opsfelder Araújo
2009-05-01 9:18 ` Peter Stephenson
2009-05-04 15:58 ` Murilo Opsfelder Araújo
2009-05-05 15:36 ` Peter Stephenson
2009-05-05 15:40 ` Clint Adams [this message]
2009-05-05 15:48 ` 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=20090505154016.GA19068@scru.org \
--to=clint@zsh.org \
--cc=mopsfelder@gmail.com \
--cc=zsh-workers@sunsite.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).