The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: ron minnich <rminnich@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: shell escapes in utilities
Date: Tue, 1 Aug 2023 11:37:41 -0400	[thread overview]
Message-ID: <CAC20D2OGEy-GXqG6ZfihdwkFmH3yb5TfUF22X-ZgsrBvsUEkuw@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYJZv=tThsACn3sRvV0HXRYG_GLuUtWkxVk_n5XhuN1UpA@mail.gmail.com>

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

Ron

I never understood why sendmail needed it.  [Actually I never really
understand sendmail's need but that's another discussion and discussion
I've had with Ertc over the years]. But shell escape were pretty typical,
until Kulp's ^Z job control stuff and/or real window managers - it would
have sucked not to have had them.
Off the top of my head:

   - any editor (text or graphical)
   - things that controlled the screen like more(1) would have wanted to
   support something like this
   - programs that produced graphical output -- from *roff/tex and the
   like, to many/most of the CAD programs, or even Ghostscript I think.  You
   might want to dump out and suck back in something processed from another
   program, and the 'pipeline' was not always the easy/right way to do that.
   Classic example of calling on the PS/EPS tools from inside of troff.  This
   is why tools like xdvi and the like supported it.
   - long-running games where you did not want to lose your session
   - many things that supported remote job entry/execution - which was
   really common in the old days [hence UUCP, the PWB RJE tools, rsh and the
   like].  IICR there was a couple of versions of telnet/supdup that could do
   it.

Clem
ᐧ
ᐧ

On Tue, Aug 1, 2023 at 1:48 AM ron minnich <rminnich@gmail.com> wrote:

> I got to wondering, based on the sendmail discussions, how many shell
> escapes have appeared over the years?
>
> uucp
> sendmail
> xdvi : "The "allowShell" option enables the shell escape in PostScript
> specials"
>
> There must be a lot of them, however.
>

[-- Attachment #2: Type: text/html, Size: 2947 bytes --]

  parent reply	other threads:[~2023-08-01 15:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  5:47 [TUHS] " ron minnich
2023-08-01 11:38 ` [TUHS] " Leah Neukirchen
2023-08-01 12:31   ` G. Branden Robinson
2023-08-01 20:33   ` Dave Horsfall
2023-08-01 20:40     ` arnold
2023-08-01 14:29 ` Skip Tavakkolian
2023-08-01 15:30   ` ron minnich
2023-08-01 18:43     ` Ron Natalie
2023-08-01 18:55       ` Niklas Karlsson
2023-08-01 20:48         ` Steffen Nurpmeso
2023-08-01 21:11           ` Ron Natalie
2023-08-01 21:52             ` Steffen Nurpmeso
2023-08-01 21:13           ` Niklas Karlsson
2023-08-01 21:19         ` Dave Horsfall
2023-08-02  3:01         ` Grant Taylor via TUHS
2023-08-02  3:42           ` Niklas Karlsson
2023-08-02  2:59       ` Grant Taylor via TUHS
2023-08-02 10:49         ` Rich Salz
2023-08-02 14:49           ` Grant Taylor via TUHS
2023-08-02 14:20         ` Clem Cole
2023-09-19 16:56     ` Ori Bernstein
2023-09-19 17:04       ` ron minnich
2023-08-01 15:36 ` Phil Budne
2023-08-01 15:37 ` Clem Cole [this message]
2023-08-01 15:37 ` Grant Taylor via TUHS

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=CAC20D2OGEy-GXqG6ZfihdwkFmH3yb5TfUF22X-ZgsrBvsUEkuw@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=rminnich@gmail.com \
    --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).