From: Kim Phillips <kim.phillips@freescale.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] contrib/completion: remove parentheses from prompt
Date: Fri, 22 Apr 2011 18:43:34 -0500 [thread overview]
Message-ID: <20110422184334.98ce52a6.kim.phillips@freescale.com> (raw)
In-Reply-To: <7vk4elnchw.fsf@alter.siamese.dyndns.org>
On Fri, 22 Apr 2011 15:32:27 -0700
Junio C Hamano <gitster@pobox.com> wrote:
> Kim Phillips <kim.phillips@freescale.com> writes:
>
> > Save horizontal terminal line real estate by removing parentheses from
> > the prompt branch display. The branch is already sufficiently visually
> > delimited by the preceding space character.
>
> That changes behaviour and makes people who like the current output
> unhappy, no? For example, I have
>
> PS1=': \h \W$(__git_ps1 "/%s"); '
>
> and from it I get these output:
>
> : host git.git/master;
> : host git.git/(v1.7.5-rc3);
> : host git.git/(63e4ee5...);
>
> I do like the fact that the tagname v1.7.5-rc3 is parenthesized---it makes
> it very clear that I am not on any branch while being detached.
>
> Of course that is _my_ personal taste, but I wonder if you can remove the
> parentheses by changing the way you use __git_ps1 in your PS1 definition.
Oh I see what happened. A long time ago I had changed the recommended
PS1 from the top of git-completion.bash to a version without the
parentheses, but I must've started working in detached states more
recently until finally _my_ personal distaste for parens kicked in
again.
Fwiw, especially on properly managed projects, the content of the name
itself is enough to distinguish a branch name from a tag name (which
usually contains a version value), from a raw sha followed by three
dots. But I'd understand if people want it to be more deterministic.
Thanks,
Kim
prev parent reply other threads:[~2011-04-22 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 19:32 [PATCH] contrib/completion: remove parentheses from prompt Kim Phillips
2011-04-22 22:32 ` Junio C Hamano
2011-04-22 23:43 ` Kim Phillips [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=20110422184334.98ce52a6.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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).