Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Andy Kosela <akosela@andykosela.com>
To: Adam Thornton <athornton@gmail.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] What is your prompt? (was: ksh88 source code?)
Date: Thu, 23 Dec 2021 07:59:57 +0100	[thread overview]
Message-ID: <CALMnNGjpf2vwL6brDM3jOuawrrspiaFG=+X8cZem+y25WWvrsA@mail.gmail.com> (raw)

On 12/22/21, Adam Thornton <athornton@gmail.com> wrote:
> MacOS finally pushed me to zsh.  So I went all the way and installed
> oh-my-zsh.  It makes me feel very dirty, and I have a two-line prompt (!!),
> but I can't deny it's convenient.
>
> tickets/DM-32983 ✗
> adam@m1-wired:~/git/jenkins-dm-jobs$
>
> (and in my terminal, the X glyph next to my git branch showing the status
> is dirty is red while the branch name is green)
>
> and if something doesn't exit with rc=0...
>
> adam@m1-wired:~/git/jenkins-dm-jobs$ fart
> zsh: command not found: fart
> tickets/DM-32983 ✗127 ⚠️
> adam@m1-wired:~/git/jenkins-dm-jobs$
>
> Then I also get the little warning glyph and the rc of the last command in
> my prompt.
>
> But then I'm also now using Fira Code with ligatures in my terminal, so
> I've pretty much gone full Red Lightsaber.

I try to keep my prompt as simple as possible.  For years I have been using:

  moon $

That 's it.  No fancy colors, not even displaying current working
directory.  I have an alias 'p' for that.

--Andy
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

             reply	other threads:[~2021-12-23  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23  6:59 Andy Kosela [this message]
2021-12-23 12:04 ` John P. Linderman
2021-12-23 19:30 ` Nemo Nusquam
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='CALMnNGjpf2vwL6brDM3jOuawrrspiaFG=+X8cZem+y25WWvrsA@mail.gmail.com' \
    --to=akosela@andykosela.com \
    --cc=athornton@gmail.com \
    --cc=coff@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).