From: "Claes Wallin (韋嘉誠)" <gnu@clacke.user.lysator.liu.se>
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix environment & PS1
Date: Wed, 1 Jul 2015 19:07:20 +0200 [thread overview]
Message-ID: <CAGv_=BqzidUUPM1fyRaybZrUbY2SsFf9C8MmwCkB-OS2_kPDAQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ=RwfYJkDSgtk2V--O0eH-eZSH1X+9U496H1YQMSOQS0Kp+kg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Jul 1, 2015 4:02 PM, "Thompson, David" <dthompson2@worcester.edu> wrote:
> On Wed, Jul 1, 2015 at 9:10 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> > I reckon it has the unfortunate property of not working out of the box
> > (except on GuixSD.) I’m sure many tools these days would choose to
> > hard-code a fancy colored PS1; while I prefer things that work out of
> > the box, I’m not comfortable with hard-coding such things.
> >
> > Thoughts?
>
> I agree with you. I'd rather not hard-code some fancy PS1.
Leaving power PS1 to power users is the reasonable thing to do. Colored
path and username etc is fine, but every user has their own ideas on where
git branch and other things ought to go.
[-- Attachment #2: Type: text/html, Size: 958 bytes --]
prev parent reply other threads:[~2015-07-01 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 21:41 [PATCH] guix environment: add a '--env-name' option Cyril Roelandt
2015-06-25 11:45 ` guix environment & PS1 Ludovic Courtès
2015-06-25 12:02 ` Ricardo Wurmus
2015-06-25 13:04 ` Thompson, David
2015-06-25 13:28 ` Ricardo Wurmus
2015-06-25 20:00 ` Claes Wallin (韋嘉誠)
2015-06-25 20:40 ` Claes Wallin (韋嘉誠)
2015-06-29 8:41 ` Ludovic Courtès
2015-06-29 10:04 ` Claes Wallin (韋嘉誠)
2015-06-25 13:02 ` Thompson, David
2015-07-01 13:10 ` Ludovic Courtès
2015-07-01 13:59 ` Thompson, David
2015-07-01 17:07 ` Claes Wallin (韋嘉誠) [this message]
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='CAGv_=BqzidUUPM1fyRaybZrUbY2SsFf9C8MmwCkB-OS2_kPDAQ@mail.gmail.com' \
--to=gnu@clacke.user.lysator.liu.se \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.