From: "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com>
To: "David's Lightspeed Email" <dpainter@lightspeed.net>,
<cygwin@sourceware.cygnus.com>
Subject: Re: One more thing. . . SH, BASH, and KSH
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <001301be6da9$9cb74670$2a68d1d0@hunda> (raw)
Message-ID: <19990331194500._o-7xtbM9-IGTuUqtrOTyJHbP-XB-TlKeNl5Z9XHKhA@z> (raw)
I will give a friendly advice:
Do some Internet searches.
There are documents available for all the UNIX shells at Internet from
various sites.
The bash is from GNU. Go to:
http://www.gnu.org/manual/bash-2.02/html_chapter/bashref_toc.html
and you will find all the answers to your questions about bash.
Suhaib
-----Original Message-----
From: David's Lightspeed Email <dpainter@lightspeed.net>
To: cygwin@sourceware.cygnus.com <cygwin@sourceware.cygnus.com>
Date: Saturday, March 13, 1999 4:40 PM
Subject: One more thing. . . SH, BASH, and KSH
>
> March 13th, 1999
>
>Oh yeah, one more thing. . . Could someone elaborate on the differences on
>fuctionality between the BASH and the SH? I understand how SH and KSH fit
>together, but I don't see how BASH fits into this picture.
>
>Most of what I've been reading about has been KSH '93. Is there a KSH
>version newer than 1993?
>
>Thanks!
> David L. Painter
> dpainter@prontomail.com
> dpainter@lightspeed.net
> ph: (559) 292-5366 * 3
> fax:(559) 292-0410
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-03-31 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-13 15:31 Suhaib M. Siddiqi [this message]
1999-03-31 19:45 ` Suhaib M. Siddiqi
-- strict thread matches above, loose matches on Subject: below --
1999-03-13 13:40 David's Lightspeed Email
1999-03-13 20:44 ` John A. Turner
1999-03-31 19:45 ` John A. Turner
1999-03-31 19:45 ` David's Lightspeed Email
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='001301be6da9$9cb74670$2a68d1d0@hunda' \
--to=ssiddiqi@inspirepharm.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=dpainter@lightspeed.net \
/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).