From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: <koen.van_hoof@alcatel.be>,
"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: TERMCAP problem.
Date: Wed, 17 Jan 2001 10:53:33 +0300 [thread overview]
Message-ID: <000001c0805a$97397130$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <Tc0a8890c5124fd0fa1@mailsweeper01.cambridgesiliconradio.com>
>
> It's changed since then. If you have HAVE_PUTENV defined in config.h, try
> undefining it for something a bit more like (but not identical to) the old
> behaviour to see if that makes a difference.
>
I believe, I know what happens. When zsh creates parameters from environment,
it splits env string in-place; when tgetent is called (from init_term from
termsetfn), envronment string for TERM looks like
TERM\0xterm
Obviously, tgetent (or some functions called from it) does not like this. But
it was there for at least half an year already. I am not sure, but I think, it
was there before my patch as well.
I'll send a patch later, hopefully today.
-andrej
next prev parent reply other threads:[~2001-01-17 7:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 10:14 koen van hoof
2001-01-15 15:46 ` Dan Nelson
2001-01-15 17:23 ` Bart Schaefer
2001-01-16 8:30 ` koen van hoof
2001-01-16 8:52 ` Andrej Borsenkow
2001-01-16 10:42 ` koen van hoof
2001-01-16 10:54 ` Peter Stephenson
2001-01-16 11:19 ` Andrej Borsenkow
2001-01-16 11:56 ` koen van hoof
2001-01-16 12:11 ` Andrej Borsenkow
2001-01-16 16:27 ` koen van hoof
2001-01-16 17:05 ` Peter Stephenson
2001-01-17 7:46 ` koen van hoof
2001-01-17 7:53 ` Andrej Borsenkow [this message]
2001-01-17 18:41 ` Some general problems with exporting cariables (Was: TERMCAP problem. ) Andrej Borsenkow
2001-01-18 12:34 ` koen van hoof
2001-01-18 13:16 ` Andrej Borsenkow
2001-01-18 15:54 ` koen van hoof
2001-01-19 15:05 ` Andrej Borsenkow
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='000001c0805a$97397130$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=koen.van_hoof@alcatel.be \
--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).