From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Environ handling broken on Cygwin RE: Cygwin: environ problem
Date: Mon, 24 Jul 2000 11:57:08 +0100 [thread overview]
Message-ID: <0FY7004QY7R77K@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Mon, 24 Jul 2000 14:39:08 +0400." <000c01bff55b$6575ef00$21c9ca95@mow.siemens.ru>
Andrej wrote:
> As I understand, the sole requirement of current code is to be able to
> unset environment variable. Cygwin provides unsetenv() function. So, we
> could retain current code on Unix and use native Cygwin function there.
>
> Any suggestions before I start hacking? :-)
Feel free. Obviously the best solution would be the minimal changes to use
putenv, getenv and unsetenv where zsh digs around directly in environ with
#ifdef __CYGWIN__. If this works, we can start adding configure checks to
see if we can do it elsewhere, since anything that reduces the number of
assumptions about the system is good. However, `if this works' may not be
a particularly well-defined test.
Let me know if you want sourceforge developer stuff adding.
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-07-24 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-21 11:56 Andrej Borsenkow
2000-07-21 13:11 ` Peter Stephenson
2000-07-21 13:39 ` Andrej Borsenkow
2000-07-24 8:14 ` Andrej Borsenkow
2000-07-24 10:39 ` Environ handling broken on Cygwin " Andrej Borsenkow
2000-07-24 10:57 ` Peter Stephenson [this message]
2000-07-25 10:49 ` Andrej Borsenkow
2000-08-16 13:28 ` Sourceforge development account Andrej Borsenkow
2000-08-16 13:35 ` Thomas Köhler
2000-08-16 13:41 ` Peter Stephenson
2000-08-21 1:25 ` Chmouel Boudjnah
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=0FY7004QY7R77K@la-la.cambridgesiliconradio.com \
--to=pws@cambridgesiliconradio.com \
--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).