From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: <greg@klanderman.net>, "Zsh list" <zsh-workers@sunsite.auc.dk>
Subject: RE: problems with 3.1.9 on cygwin
Date: Wed, 11 Oct 2000 10:14:46 +0400 [thread overview]
Message-ID: <000001c0334a$8d87fd30$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <14819.63135.137957.342501@phl.itasoftware.com>
>
> Hello,
>
> So I just noticed that 3.1.9 is advertised to work under cygwin...
> but is it supposed to work *well* yet?
>
> I notice that "echo *" seems to only ever yield "no matches found".
>
mw1g017@MW1G17C% echo *
DocReader.exe ctags.exe docreader.ini gvim.exe iSiloC32.exe runzsh.bat
runzsh.ba
t~ vimrun.exe xxd.exe
> And there seems to be a bug where setting (but not exporting) a
> variable in one script and 'source'ing another does not result in the
> second script seeing that variable. But I've not been able to
> reproduce this with a succinct example.
>
mw1g017@MW1G17C% cat foo.zsh
#!/bin/zsh
foo=1234
source /tmp/bar.zsh
mw1g017@MW1G17C% cat bar.zsh
#!/bin/zsh.exe
echo $foo
mw1g017@MW1G17C% source foo.zsh
1234
Could you provide example of script that exibits an error?
> Can someone fill me in on the state of cygwin support?
>
Well, I cannot comment on stock 3.1.9 at all. Current CVS version does work;
3.1.9-dev-6 should work OOTB if you have recent enough Cygwin version (with
one minor problem). I use (and ported it :-) under cygwin-1.1.4 and
binutils-20000722-1.
I must admint, I do not spend much time in Zsh under Cygwin, but almost all
regression tests passed (failed are related to unsupported features).
-andrej
next prev parent reply other threads:[~2000-10-11 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-11 5:11 Greg Klanderman
2000-10-11 6:14 ` Andrej Borsenkow [this message]
2000-10-13 0:05 ` Greg Klanderman
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='000001c0334a$8d87fd30$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=greg@klanderman.net \
--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).