The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Shell Level...
Date: Mon, 20 Jan 2020 15:55:47 -0800	[thread overview]
Message-ID: <m1itgtX-0036tPC@more.local> (raw)
In-Reply-To: <1itSE0-5Td-00@marmaro.de>

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

At Mon, 20 Jan 2020 09:15:56 +0100, markus schnalke <meillo@marmaro.de> wrote:
Subject: Re: [TUHS] Shell Level...
>
> What's the use of it? The only use of $SHLVL I can think of is the
> answer to the question if ^D will close the last shell or just a
> sub shell. I hardly ever ask myself this question. Probably that
> starts to become relevant when you open sub shells frequently.

I've always just used "set ignoreeof" (first in Csh and later in Ksh),
but just in my initial login shell (i.e. set in ~/.login), to prevent ^D
from logging me out.

--
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2020-01-20 23:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 21:22 Grant Taylor via TUHS
2020-01-19 23:21 ` Thomas Paulsen
2020-01-20  8:15 ` markus schnalke
2020-01-20  8:39   ` Kurt H Maier
2020-01-21 20:42     ` Grant Taylor via TUHS
2020-01-20 19:40   ` Theodore Y. Ts'o
2020-01-20 23:51     ` Terry Jones
2020-01-21 20:44     ` Grant Taylor via TUHS
2020-01-21 23:10       ` Theodore Y. Ts'o
2020-01-20 23:55   ` Greg A. Woods [this message]
2020-01-21 20:46     ` Grant Taylor via TUHS
2020-01-21 23:39       ` Greg A. Woods
2020-01-20 23:43 ` Greg A. Woods

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=m1itgtX-0036tPC@more.local \
    --to=woods@robohack.ca \
    --cc=tuhs@tuhs.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 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).