From: "vipin aravind" <vipin.aravind@wipro.com>
To: <zsh-workers@sunsite.dk>
Subject: Zshell for win32
Date: Tue, 20 Mar 2001 14:31:50 +0530 [thread overview]
Message-ID: <009f01c0b11c$6918d690$b90806c0@wipro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
hi all,
I know this is not the place to put up something on win32.
It becomes necessary for me to get the suggestions on it before I embark
on the port.
Find enclosed a pre-mature features list for the shell I name Zshell32.
thank you
vipin
[-- Attachment #2: features.txt --]
[-- Type: text/plain, Size: 1321 bytes --]
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.
Feature List for Zshell32:-
Iam not optimistic in getting an exact port of zshell for native win32.
Ofcourse zshell can be compiled and run in the cygwin environment.
But the goal here isto provide a shell based on Zshell for native win32
similar to existing cmd.exe and other commercial shells like 4nt,4dos.
Certain factors like NO forking in win32 puts a severe limit on the
port.
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.
2) First release will support no extra modules and multilanguage support.
Features that will be supported:-
1) All the current Zshell programming syntax.
2) similar startup scripts as in unix.
Iam yet to draw up a TODO list.
I will be needing lot of help from all of you after I come up with the TODO list
next reply other threads:[~2001-03-20 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-20 9:01 vipin aravind [this message]
2001-03-20 18:32 ` Bart Schaefer
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='009f01c0b11c$6918d690$b90806c0@wipro.com' \
--to=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).