zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Zshell for win32
Date: Wed, 21 Mar 2001 10:55:38 +0000	[thread overview]
Message-ID: <Tc0a88d01526d435d5e@mailsweeper01.cambridgesiliconradio.com> (raw)
In-Reply-To: Your message of "Wed, 21 Mar 2001 11:29:55 +0300." <Pine.SV4.4.33.0103211123030.24335-100000@itsrm2.mow.siemens.ru>

Andrej write
> On Tue, 20 Mar 2001, Bart Schaefer wrote:
> > On Mar 20,  2:31pm, vipin aravind wrote:
> > }   Certain factors like NO  forking in win32 puts a severe limit on the
> > }   port.
> >
> > I thought Amol's code had a pretty good fork emulation built into it; in
> > fact unless I'm very much mistaken I've had some success using that fork
> > emulation in porting other (smaller) unix programs to win32.
> >
> 
> I wonder, what are the benefits of Win32 version against Cygwin
>  one? Zsh relies heavily on Unix semantic; to implement something that can
> be called Zsh(-clone) on Win32 you need an emulation layer - and that is
> exactly what Cygwin does. Creating Yet Another Unix Emulation on Win32
> does not look very promising. And you need just a single DLL to run Cygwin
> program (you do not need to install the whole Cygwin).

There's a lot in this.  It might be worth considering having COMMAND.COM
builtin support (which I presume is going to be essential in this case)
via a module.

However, that still leaves some basic syntactic incompatilibilty if the
intention is a drop-in replacement for the DOS shell (which it still pretty
much what that object is, unfortunately).  That's a tough nut to crack in
any case.  The problems are how to interpret backslashes on the command
line, and so on.  The more like the original you need to be, the less this
is going to be like the real zsh under Cygwin, and the more necessary it is
to rewrite the internals.  That doesn't have to stop it running under
Cygwin, however, though as Bart says calling it anything like zshell is a
bit confusing.  (How about zcommand, or zcom or zwin if that's too long?)

> What do you mean under "multilanguage support"? We do not have any as of
> now.

I interpret that as locale support.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


  reply	other threads:[~2001-03-21 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-20  9:01 vipin aravind
2001-03-20 18:32 ` Bart Schaefer
2001-03-21  8:29   ` Andrej Borsenkow
2001-03-21 10:55     ` Peter Stephenson [this message]
2001-03-21 10:16   ` vipin aravind

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=Tc0a88d01526d435d5e@mailsweeper01.cambridgesiliconradio.com \
    --to=pws@csr.com \
    --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).