From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "vipin aravind" <vipin.aravind@wipro.com>, <zsh-workers@sunsite.dk>
Subject: Re: Zshell for win32
Date: Tue, 20 Mar 2001 18:32:33 +0000 [thread overview]
Message-ID: <1010320183233.ZM16084@candle.brasslantern.com> (raw)
In-Reply-To: <009f01c0b11c$6918d690$b90806c0@wipro.com>
On Mar 20, 2:31pm, vipin aravind wrote:
} Subject: Zshell for win32
}
} Zshell32:- This is going to be a port of unix open source shell(Zshell)
} The idea of the port is to evolve an open source shell for native win32.
} It will be based heavily on Zshell(3.1.9 or 4.0.1). Future versions of
} Zshell32 will be based on the Zshell port of 3.1.9 or 4.0.1 and not on future
} versions of zshell.This is important for Zshell32 to evolve in win32.
If what you're creating is not going to be zsh, then it should not have
a name resembling zsh or zshell. I'm willing to give you all the help
I can to produce a win32 port of zsh that will at least track, and ideally
could be folded into, the regular zsh sources -- but I'm not pleased at
the idea of wading through questions from confused windows users who don't
know that the shell they have is not really zsh.
} 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.
} Features that won't be supported:-
} 1) No ksh and Bourne shell emulation.
} Instead provide cmd emulation and provide the necessary entry points
} to emulate any other shells for win32.
It's going to be a lot more work to remove the sh/ksh emulation than to
leave it alone. Why would you want to take it out?
} 2) First release will support no extra modules and multilanguage
} support.
Not surprising, though the cygwin build should provide some hints on how
to construct DLLs for the modules.
} Features that will be supported:-
} 1) All the current Zshell programming syntax.
} 2) similar startup scripts as in unix.
A reasonable start.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-03-20 18:34 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 [this message]
2001-03-21 8:29 ` Andrej Borsenkow
2001-03-21 10:55 ` Peter Stephenson
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=1010320183233.ZM16084@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=vipin.aravind@wipro.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).