From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: configure.in: tgetent test does not work on Cygwin
Date: Wed, 26 Jul 2000 16:06:51 +0100 [thread overview]
Message-ID: <0FYB0065C8NEFM@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Wed, 26 Jul 2000 15:43:03 +0400." <000801bff6f6$a81e9ef0$21c9ca95@mow.siemens.ru>
> I noted, that current bash under Cygwin automatically prepends
> /usr/bin:/usr/local/bin to PATH (BTW it also has cool default prompt as well
> :-) May be, we could do the same for zsh. It looks, like Cygwin directory
> structure has stabilized (at least, if you use setup, you do get /bin and
> /usr/bin).
We can make $PATH more configurable, but I'm not sure I like the idea of
automatically adding something to an existing imported path, except in a
startup file.
Anyway, this doesn't fix the startup problem, of course, since the DLL is
searched for before we've touched the path. I imagine bash works because
it's in the same directory.
--
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-26 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1D4512C91A0E044FBF24DDB221C94C53826756@red-msg-29.redmond.corp.microsoft.com>
2000-07-25 12:30 ` Problems with zsh 3.1.9 and cygwin Andrej Borsenkow
2000-07-25 17:07 ` Problems under domain account on Win2k " Andrej Borsenkow
2000-07-25 18:35 ` Tomislav Goles
2000-07-26 8:23 ` PATCH: configure.in: tgetent test does not work on Cygwin Andrej Borsenkow
2000-07-26 9:07 ` Peter Stephenson
2000-07-26 10:15 ` Andrej Borsenkow
2000-07-26 10:50 ` Peter Stephenson
2000-07-26 11:26 ` Peter Stephenson
2000-07-26 11:43 ` Andrej Borsenkow
2000-07-26 15:06 ` Peter Stephenson [this message]
2000-07-26 18:03 ` 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=0FYB0065C8NEFM@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).