From: Greg 'groggy' Lehey <grog@lemis.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: coff <coff@minnie.tuhs.org>, Rudi Blom <rudi.j.blom@gmail.com>
Subject: Re: [COFF] What is your prompt?
Date: Sun, 26 Dec 2021 10:19:41 +1100 [thread overview]
Message-ID: <20211225231941.GB83649@eureka.lemis.com> (raw)
In-Reply-To: <Ycag2OQte63ONj39@mit.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]
On Friday, 24 December 2021 at 23:40:56 -0500, Theodore Ts'o wrote:
> Here are examples of some of my prompts. It does use two lines, but
> the extra context is worth it to me:
>
> <tytso@cwcc> {/home/tytso}
> 267% cd /usr/projects/e2fsprogs/base
That's actually surprisingly like mine, though I squeeze it into one
line. Like you, I find user, system and cwd important, but also the
tty. In addition I put a marker to help find prompts in long output,
so a typical prompt might be:
=== grog@bilbo (/dev/pts/27) ~/src 6 ->
That's generated with
PS1="\[ESC[34m\]=== \u@\h (`tty`) \[ESC[31m\]\w\[ESC[34m\] \# ->\[ESC[30m\]\[ESC[47m\] "
> 272% su
> Password:
> <tytso.root@cwcc> {/home/tytso}, level 2
That's interesting. How do you do that?
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-12-25 23:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 2:50 Rudi Blom
2021-12-25 4:40 ` Theodore Ts'o
2021-12-25 17:39 ` Steffen Nurpmeso
2021-12-25 18:28 ` Grant Taylor via COFF
2021-12-25 19:14 ` Steffen Nurpmeso
2021-12-26 3:44 ` Grant Taylor via COFF
2021-12-25 23:19 ` Greg 'groggy' Lehey [this message]
2021-12-25 23:43 ` Steffen Nurpmeso
2021-12-26 21:18 ` Theodore Ts'o
2021-12-26 21:33 ` Warner Losh
2021-12-27 1:33 ` Theodore Ts'o
2021-12-27 2:52 ` Rudi Blom
2021-12-27 3:43 ` Greg 'groggy' Lehey
2021-12-27 4:06 ` Rudi Blom
2021-12-27 4:12 ` Greg 'groggy' Lehey
2021-12-27 4:28 ` Rudi Blom
2021-12-27 18:44 ` Steffen Nurpmeso
2021-12-27 18:55 ` Warner Losh
2021-12-27 19:07 ` Grant Taylor via COFF
2021-12-27 19:25 ` Steffen Nurpmeso
2021-12-27 18:37 ` Steffen Nurpmeso
2021-12-26 3:29 ` Grant Taylor via COFF
2021-12-26 3:54 ` Greg 'groggy' Lehey
2021-12-26 5:27 ` Grant Taylor via COFF
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 6:59 [COFF] What is your prompt? (was: ksh88 source code?) Andy Kosela
2021-12-24 17:17 ` [COFF] What is your prompt? Grant Taylor via COFF
2021-12-26 22:17 ` Mike Markowski
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=20211225231941.GB83649@eureka.lemis.com \
--to=grog@lemis.com \
--cc=coff@minnie.tuhs.org \
--cc=rudi.j.blom@gmail.com \
--cc=tytso@mit.edu \
/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).