The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: <ron@ronnatalie.com>
To: "'Brian Zick'" <brian@zick.io>, <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Origins of shell prompt suffixes % $ > #
Date: Mon, 6 Aug 2018 17:16:21 -0400	[thread overview]
Message-ID: <01c101d42dca$baa2eb70$2fe8c250$@ronnatalie.com> (raw)
In-Reply-To: <1533588813.1868321.1465431536.01CE36BC@webmail.messagingengine.com>

The early shells (Thompson, Mashey)  used "% " for regular user (and # for root).   The Thompson shell didn't have a setable prompt.
The Bourne shell (V7) had setable PS1 (start of command) and PS2 (continuation prompts) and set the to "$ " and "> " respectively.    Again # was used for root.


-----Original Message-----
From: TUHS <tuhs-bounces@minnie.tuhs.org> On Behalf Of Brian Zick
Sent: Monday, August 6, 2018 4:54 PM
To: tuhs@minnie.tuhs.org
Subject: [TUHS] Origins of shell prompt suffixes % $ > #

Hi,

I usually just lurk on this list, but I've been curious lately about the origin of the symbols at the end of various interactive prompts.

ksh (etc), bash, sh use $ for non-root, and # for root

csh, tcsh and zsh use % for non-root and # for root

fish and things like mysql, ftp, and interactive shells for a lot of scripting languages use >

rc uses ;

Where do these different conventions originate?

B


  reply	other threads:[~2018-08-06 21:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06 20:53 Brian Zick
2018-08-06 21:16 ` ron [this message]
2018-08-06 21:33   ` Henry Bent
2018-08-07  1:10     ` George Michaelson
2018-08-07  1:12       ` ron
2018-08-07  1:10     ` ron
2018-08-07  6:54 ` Michael Kjörling
2018-08-07  8:02   ` Michael Kjörling
2018-08-07  8:23     ` Dave Horsfall
2018-08-07  8:37       ` KatolaZ
2018-08-07 10:45     ` Tony Finch
2018-08-07 17:35       ` Lyndon Nerenberg
2018-08-08 14:38       ` Nemo
2018-08-08 14:51         ` Clem Cole
2018-08-07 11:24     ` Pete Turnbull
2018-08-08 19:55     ` Derek Fawcus
2018-08-07  7:31 ` Kurt H Maier
2018-08-07  7:50   ` arnold
2018-08-07  7:57   ` Bakul Shah
2018-08-07 15:15   ` Brian Zick
2018-08-07 15:52     ` John P. Linderman
2018-08-07 18:09     ` Cág
2018-08-07 18:51       ` arnold
2018-08-07 19:00         ` Cág
2018-08-07 19:06           ` Brian Zick
2018-08-07 12:34 Doug McIlroy
2018-08-08 15:20 Noel Chiappa
2018-08-08 16:01 ` Gilles Gravier
2018-08-08 20:29   ` ron
2018-08-08 20:30   ` Clem Cole
2018-08-08 20:51     ` Warner Losh
2018-08-09  2:50   ` William Corcoran

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='01c101d42dca$baa2eb70$2fe8c250$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    --cc=brian@zick.io \
    --cc=tuhs@minnie.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).