The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: The Unix Heritage Society <tuhs@minnie.tuhs.org>
Subject: [TUHS] Shell Level...
Date: Sun, 19 Jan 2020 14:22:29 -0700	[thread overview]
Message-ID: <f8fe34ae-e3e3-dfbd-8bc8-15bc58474062@spamtrap.tnetconsulting.net> (raw)

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

Hi,

Have you ever used shell level, $SHLVL, in your weekly ~> daily use of Unix?

I had largely dismissed it until a recent conversation in a newsgroup. 
I learned that shelling out of programs also increments the shell level. 
  I.e. :shell or :!/bin/sh in vim.

Someone also mentioned quickly starting a new sub-shell from the current 
shell for quick transient tasks, i.e. dc / bc, mount / cp / unmount, 
{,r,s}cp, etc., in an existing terminal window to avoid cluttering that 
first terminals history with the transient commands.

That got me to wondering if there were other uses for shell level 
($SHLVL).  Hence my question.

This is more about using (contemporary) shells on Unix, than it is about 
Unix history.  But I suspect that TUHS is one of the best places to find 
the most people that are likely to know about shell level.  Feel free to 
reply to COFF if it would be better there.



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]

             reply	other threads:[~2020-01-19 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 21:22 Grant Taylor via TUHS [this message]
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
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=f8fe34ae-e3e3-dfbd-8bc8-15bc58474062@spamtrap.tnetconsulting.net \
    --to=tuhs@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.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 NNTP newsgroup(s).