From: Alexey Vatchenko <avv@mail.zp.ua>
To: zsh-workers@sunsite.dk
Subject: Re: Version 4.2.2 of zsh released
Date: Thu, 13 Jan 2005 14:47:28 +0200 [thread overview]
Message-ID: <41E66DE0.2040901@mail.zp.ua> (raw)
In-Reply-To: <200501131030.j0DAULdg029924@news01.csr.com>
Peter Stephenson wrote:
> Alexey Vatchenko wrote:
>
>>Where can i get NT port of last zsh? (AFAIK Cygwin Zsh != NT port Zsh)
>
> You're correct that the Cygwin version isn't the same as native NT
> (2000, XP). However, the changes to compile natively under Windows are
> substantial and Cygwin have done most of the work for us. Furthermore,
> you won't get very far with any of the supplied functions without a set
> of Unix tools, and they assume Unix file name semantics. In short,
> Cygwin is almost certainly your best bet.
I use zsh 3.0.5-nt-beta-0.75 and *very happy* about Unix name semantics.
And i use it exactly because of Unix name semantics. But there are some
bugs in that version (which i tried to fix manually, and i have
quick-n-dirty fixed some).
I use Unix utilities from http://unxutils.sourceforge.net/. They are
very happy about Unix name semantics too. Even vim likes it.
The main reason i use Unix name semantics is Windows understands it too.
Cygwin, in other hand, uses names that actually does not exist in
system. And that's why i don't like Microsoft Services for Unix as well.
> As far as I know the older zsh that ran natively under Windows isn't
> being maintained.
too bad!
--
%kill -9 `ps ax | grep "BUG" | awk '{print $1}'`;
echo debugged | mail -s "gdb" avv@mail.zp.ua
next prev parent reply other threads:[~2005-01-13 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501121257.j0CCvDS4024242__47538.8375147761$1105534784$gmane$org@news01.csr.com>
2005-01-13 8:19 ` Alexey Vatchenko
2005-01-13 10:30 ` Peter Stephenson
2005-01-13 12:47 ` Alexey Vatchenko [this message]
2005-01-13 13:03 ` Alexey Vatchenko
[not found] <200501121257.j0CCvDS4024242@news01.csr.com>
2005-01-12 16:27 ` Oliver Kiddle
2005-01-12 20:00 ` Wayne Davison
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=41E66DE0.2040901@mail.zp.ua \
--to=avv@mail.zp.ua \
--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).