All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] git-prompt.sh: strip unnecessary space in prompt string
Date: Sun, 12 May 2013 21:57:19 -0700	[thread overview]
Message-ID: <7v61ynsci8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1368289513-8700-2-git-send-email-artagnon@gmail.com

Ramkumar Ramachandra <artagnon@gmail.com> writes:

> Nobody has branch names that end with + or *.  Then why put a space
> after the branch name and before [*|+][=|<|>] in the prompt string?

I do not think the space is for disambiguation.

It is like asking why typeset a space after a sentence a tad wider
than a space after each word: grouping related things together, and
separating groups of different kind apart, to make it more readable.

  reply	other threads:[~2013-05-13  4:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-11 16:25 [PATCH 0/2] Colored prompt for zsh Ramkumar Ramachandra
2013-05-11 16:25 ` [PATCH 1/2] git-prompt.sh: strip unnecessary space in prompt string Ramkumar Ramachandra
2013-05-13  4:57   ` Junio C Hamano [this message]
2013-05-13  7:40     ` Ramkumar Ramachandra
2013-05-13  9:17       ` SZEDER Gábor
2013-05-13 10:13         ` Ramkumar Ramachandra
2013-05-13 11:05           ` SZEDER Gábor
2013-05-13 11:11             ` SZEDER Gábor
2013-05-13 13:58               ` Junio C Hamano
2013-05-13 14:21                 ` Ramkumar Ramachandra
2013-05-11 16:25 ` [PATCH 2/2] git-prompt.zsh: introduce thin ZSH wrapper Ramkumar Ramachandra
2013-05-11 21:26   ` Felipe Contreras
2013-05-11 22:18     ` [PATCH v2] git-prompt.sh: colorize ZSH prompt Ramkumar Ramachandra
2013-05-11 22:29       ` Felipe Contreras
2013-05-11 22:40         ` Ramkumar Ramachandra
2013-05-11 23:06           ` Felipe Contreras

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=7v61ynsci8.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.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 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.