public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "David's Lightspeed Email" <dpainter@lightspeed.net>
To: <cygwin@sourceware.cygnus.com>
Subject: Job Control in the Bourne Shell
Date: Sun, 14 Mar 1999 16:16:00 -0000	[thread overview]
Message-ID: <000d01be6e78$81a297c0$b539a5d1@www.lightspeed.net> (raw)

                                    March 14th, 1999

In response to my question yesterday about Job Control in the Bourne Shell,
I've since then learned that it is included as a standard part of the shell
in SVR4 versions and later.

Thanks everyone for your feedback on the KSH yesterday.  I downloaded the
MKS version, and have been experimenting with it for the last day.

One thing to note, though, is that MKS includes the VI editor with their
package.  Why doesn't Cygwin include some equivalent of this?  For the life
of me, I hate VI and prefer Emacs.  But it is sometimes nice to have it
around for quick editing on the fly.  It also comes in handy for Command
Line editing too.

                                     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

WARNING: multiple messages have this Message-ID
From: "David's Lightspeed Email" <dpainter@lightspeed.net>
To: <cygwin@sourceware.cygnus.com>
Subject: Job Control in the Bourne Shell
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <000d01be6e78$81a297c0$b539a5d1@www.lightspeed.net> (raw)
Message-ID: <19990331194500.KJ68wXNrL5KkZ4q4nj4mj3AEO-E87l_Qr9aJCXsOTJ0@z> (raw)

                                    March 14th, 1999

In response to my question yesterday about Job Control in the Bourne Shell,
I've since then learned that it is included as a standard part of the shell
in SVR4 versions and later.

Thanks everyone for your feedback on the KSH yesterday.  I downloaded the
MKS version, and have been experimenting with it for the last day.

One thing to note, though, is that MKS includes the VI editor with their
package.  Why doesn't Cygwin include some equivalent of this?  For the life
of me, I hate VI and prefer Emacs.  But it is sometimes nice to have it
around for quick editing on the fly.  It also comes in handy for Command
Line editing too.

                                     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


             reply	other threads:[~1999-03-14 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-14 16:16 David's Lightspeed Email [this message]
1999-03-31 19:45 ` David's Lightspeed Email
1999-03-14 16:21 Suhaib M. Siddiqi
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-15  6:08 Earnie Boyd
1999-03-31 19:45 ` Earnie Boyd

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='000d01be6e78$81a297c0$b539a5d1@www.lightspeed.net' \
    --to=dpainter@lightspeed.net \
    --cc=cygwin@sourceware.cygnus.com \
    /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).