All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mantas Mikulėnas" <grawity@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: tty swtch key
Date: Thu, 27 Mar 2014 20:40:22 +0200	[thread overview]
Message-ID: <lh1ra8$dd7$1@ger.gmane.org> (raw)
In-Reply-To: <533320C5.7040609@ubuntu.com>

On 2014-03-26 20:47, Phillip Susi wrote:
> I could have sworn that I used the tty swtch feature once many years
> ago and that it sent a special signal to the shell, causing it to be
> suspended and return you to the parent shell, as if you had entered
> the suspend command.  I can't find the signal in the man pages now,
> and using stty to set a swtch key and hitting it does nothing.  Is
> this unimplemented on linux, and if so, shouldn't the man page be
> updated to reflect that?

AFAIK, Linux never had this feature built-in. I'm not quite old enough
to have actually used it, but I've read and saved a few Usenet posts
that say `shl` ("shell layers") only existed in very old Unix versions
like SVR3, to compete with BSD-style job control.

(Looks like Google Groups removed find-by-Message-ID, unfortunately. I
guess I could just attach all of the posts...)

On the other hand, there _is_ a reimplementation of shl for Linux and
Solaris, as part of heirloom-toolchest
<http://heirloom.sourceforge.net/tools.html> and
<http://heirloom.sourceforge.net/man/shl.1.html>.

-- 
Mantas Mikulėnas <grawity@gmail.com>


  reply	other threads:[~2014-03-27 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 18:47 tty swtch key Phillip Susi
2014-03-27 18:40 ` Mantas Mikulėnas [this message]
2014-03-27 19:22   ` Phillip Susi
2014-03-27 20:12     ` Mantas Mikulėnas
2014-03-27 20:48       ` Phillip Susi
     [not found]         ` <5334B42D.1010304@gmail.com>
2014-03-28  1:47           ` Phillip Susi
2014-03-27 23:57       ` Samuel Thibault
2014-03-29  2:49   ` Dale R. Worley

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='lh1ra8$dd7$1@ger.gmane.org' \
    --to=grawity@gmail.com \
    --cc=util-linux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.