Computer Old Farts Forum
 help / color / mirror / Atom feed
From: jpl.jpl at gmail.com (John P. Linderman)
Subject: [COFF] Comparative promptology
Date: Mon, 28 Oct 2019 16:29:28 -0400	[thread overview]
Message-ID: <CAC0cEp8wNjc_PwxAr5qAq+htAgPTce7RXQehdNU=rhr=C0aLXQ@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfqQ3gq=Wtee7XOG9yhuWf7bQEhCsw1xOEvE+JgByadHtw@mail.gmail.com>

A bit off-off-topic, but as I mentioned elsewhere, I was lucky enough to
have one of the (if not *the*) first CRT terminals in the Labs. It was an
HP 264?, and it supported scrolling back to stored lines, and re-entering
them. I quickly settled in on a prompt that ended with "@", the default
"line kill", so whatever came before was ignored, and only the command that
followed was effectively re-entered. Quaint that "@" was a seldom-seen
character then.

I now have a prompt that ends with a newline. Still convenient for
copy/paste. The prompt itself has colors, separating host name from current
directory. This makes it easy to spot non-prompt line in the command line
history, and to determine which host I am connected to in that window, and
where I am on that host.


On Mon, Oct 28, 2019 at 3:57 PM Warner Losh <imp at bsdimp.com> wrote:

>
>
> On Mon, Oct 28, 2019 at 1:51 PM Lars Brinkhoff <lars at nocrew.org> wrote:
>
>> Dave Horsfall wrote:
>> > Steve Nickolas wrote:
>> >> 86-DOS actually did use ":" as a prompt character.
>> > The best I've ever seen was RT-11's "." - talk about minimalist...
>> >
>> > Actually this thread probably belongs on COFF by now.
>>
>> I was bound to happen.  List all the prompts!
>>
>> "*" seems popular on PDP-10s.
>>
>
> "@  " was the TOPS-20 prompt.
> "$ " was the VMS prompt
> RSTS/E was just "Ready\n"
>
> But none of these get us closer to CP/M's > prompt.
>
> Warner
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191028/c8ab0dc5/attachment.html>


  reply	other threads:[~2019-10-28 20:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201910272031.x9RKVSem124842@tahoe.cs.Dartmouth.EDU>
     [not found] ` <CAFH29trMHepMHK0C+UapNVXvjfnFMv5ov4W4YS+yOn4i+mhV0A@mail.gmail.com>
     [not found]   ` <CANV78LQa=VTZAMmVeRphTvrkxrkrAzgoU_-KqtdgqfWY2uUZJg@mail.gmail.com>
     [not found]     ` <51f2d838-d097-a93f-b44d-9c670d206d2b@tnetconsulting.net>
     [not found]       ` <alpine.BSF.2.02.1910272110350.28402@frieza.hoshinet.org>
     [not found]         ` <xzdtvssnnqfvfxq9swgv979g@localhost>
     [not found]           ` <alpine.BSF.2.02.1910281106290.77349@frieza.hoshinet.org>
2019-10-28 18:47             ` [COFF] [TUHS] UNIX Backslash History dave
2019-10-28 19:10               ` [COFF] Comparative promptology lars
2019-10-28 19:57                 ` imp
2019-10-28 20:29                   ` jpl.jpl [this message]
2019-10-29 10:30                   ` skogtun
2019-10-29 10:32                     ` skogtun
2019-10-30  8:19                       ` tih
2019-10-31  1:19                         ` [COFF] Fieldata characters (was: Comparative promptology) grog
2019-10-29 19:57                   ` [COFF] Comparative promptology 
2019-10-30  7:01                   ` lars
     [not found]                 ` <2daf68cb-1b16-05a5-af0c-6d64778b2da2@kilonet.net>
2019-10-28 23:13                   ` krewat
2019-10-29  5:32                     ` lars
2019-10-28 20:43               ` [COFF] [TUHS] UNIX Backslash History paul.winalski
2019-10-28 23:17                 ` krewat
2019-10-31  1:59                 ` gtaylor

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='CAC0cEp8wNjc_PwxAr5qAq+htAgPTce7RXQehdNU=rhr=C0aLXQ@mail.gmail.com' \
    --to=coff@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).