From: Chet Ramey <chet@nike.INS.CWRU.Edu>
To: khan@NanoTech.Wisc.EDU
Cc: cygwin@cygwin.com, dkarr@tcsi.com, chet@po.cwru.edu
Subject: Re: KSH is pdksh
Date: Thu, 25 Jan 2001 07:39:00 -0000 [thread overview]
Message-ID: <1010125152640.AA39045.SM@nike.INS.CWRU.Edu> (raw)
> Nope, bash is not ksh. There are quite a few ksh93 features that are not
> implemented in bash (and possibly quite a few from ksh88 days, but I
> don't have details on those).
pd-ksh doesn't implement them either. It attempts to emulate ksh88, with
a few ksh93 features that POSIX specifies.
The ksh88 and ksh93 features that bash does not implement (with suggested
bash equivalents for a few) are listed in the FAQ.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)
Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2001-01-25 7:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 7:39 Chet Ramey [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 8:21 Shields, Daniel [EQTY]
2001-01-24 13:36 Galen Boyer
2001-01-24 14:35 ` Larry Hall (RFK Partners, Inc)
2001-01-24 15:33 ` David Feustel
2001-01-24 15:30 ` Corinna Vinschen
2001-01-24 15:39 ` David M. Karr
2001-01-24 17:25 ` Earnie Boyd
2001-01-24 19:07 ` Mumit Khan
2001-01-25 8:25 ` David M. Karr
2001-01-25 8:34 ` Larry Hall (RFK Partners, Inc)
2001-01-25 12:52 ` Matthew Smith
2001-01-25 13:32 ` Earnie Boyd
2001-01-25 7:51 ` Galen Boyer
2001-01-25 13:01 ` Galen Boyer
[not found] <Mumit>
[not found] ` <Khan's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed,>
[not found] ` <24>
[not found] ` <Jan>
[not found] ` <2001>
[not found] ` <21:07:04>
[not found] ` <-0600>
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=1010125152640.AA39045.SM@nike.INS.CWRU.Edu \
--to=chet@nike.ins.cwru.edu \
--cc=chet@po.cwru.edu \
--cc=cygwin@cygwin.com \
--cc=dkarr@tcsi.com \
--cc=khan@NanoTech.Wisc.EDU \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).