From: "Michael Kjörling" <michael@kjorling.se>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Origins of shell prompt suffixes % $ > #
Date: Tue, 7 Aug 2018 06:54:54 +0000 [thread overview]
Message-ID: <20180807065453.jjnsx3cunjug5q3e@h-174-65.A328.priv.bahnhof.se> (raw)
In-Reply-To: <1533588813.1868321.1465431536.01CE36BC@webmail.messagingengine.com>
On 6 Aug 2018 21:53 +0100, from brian@zick.io (Brian Zick):
> rc uses ;
Not sure what came first, and not up to digging out the history books,
but these days, a plain `;` for a prompt has a distinct advantage in
that you can copy the whole line and paste it into another shell, and
the shell will do The Right Thing (tm) as long as (as is, I believe,
done by all of the major shells at least) it uses `;` for command
separation.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“The most dangerous thought that you can have as a creative person
is to think you know what you’re doing.” (Bret Victor)
next prev parent reply other threads:[~2018-08-07 7:04 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
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 [this message]
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=20180807065453.jjnsx3cunjug5q3e@h-174-65.A328.priv.bahnhof.se \
--to=michael@kjorling.se \
--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).