From: Miles Bader <miles@gnu.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: vc-mode-line
Date: Thu, 05 Aug 2010 13:55:39 +0900 [thread overview]
Message-ID: <buok4o5fyk4.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <yxqd3txg0dm.fsf@fencepost.gnu.org> (Dan Nicolaescu's message of "Thu, 05 Aug 2010 00:16:21 -0400")
Of course, being in the mode-line adds other constraints -- that
character it also serves as a separator, should not be too obtrusive in
"common" states (both unmodified and modified are common I think),
should not cause confusion with other parts of the modeline, etc.
In particular, I think "*" might not be such a good choice, because
using "*" for the VCS indicator would dilute the impact of the standard
"buffer modified" indicator. Right now, the buffer-modified indicator
stands out, as "*" is a fairly noticeable character; the more "*"s with
_different_ meanings we add to the modeline, the less noticeable it
becomes (and noticing whether the buffer is modified or not is important
I think).
I agree that "+" for "newly added file" seems better than @.
If changing everything is OK, how about:
":" unmodified but already in repo
"=" modified (emacs commonly associates "=" with "diff")
"+" added, but not yet committed
"-" deleted, but not yet committed
If that's too radical a change, how about (avoids redefining old chars):
"-" [existing] unmodified but already in repo
"=" modified (emacs commonly associates "=" with "diff")
"+" added, but not yet committed
"#" deleted, but not yet committed
-Miles
--
Custard, n. A vile concoction produced by a malevolent conspiracy of the hen,
the cow, and the cook.
next prev parent reply other threads:[~2010-08-05 4:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 11:53 vc-mode-line Eli Zaretskii
2010-07-30 12:34 ` vc-mode-line Andy Moreton
2010-08-01 23:04 ` vc-mode-line Stefan Monnier
2010-07-30 15:52 ` vc-mode-line Leo
2010-08-05 4:16 ` vc-mode-line Dan Nicolaescu
2010-08-05 4:55 ` Miles Bader [this message]
2010-08-05 5:20 ` vc-mode-line Dan Nicolaescu
2010-08-05 6:39 ` vc-mode-line Stephen J. Turnbull
2010-08-05 16:20 ` vc-mode-line David Kastrup
2010-08-05 14:57 ` vc-mode-line Eli Zaretskii
2010-08-05 18:54 ` vc-mode-line Dan Nicolaescu
2010-08-06 2:41 ` vc-mode-line Miles Bader
2010-08-06 3:38 ` vc-mode-line Óscar Fuentes
2010-08-06 4:59 ` vc-mode-line Óscar Fuentes
2010-08-06 5:13 ` vc-mode-line Miles Bader
2010-08-06 6:52 ` vc-mode-line Óscar Fuentes
2010-08-06 8:13 ` vc-mode-line Eli Zaretskii
2010-08-06 14:23 ` vc-mode-line Óscar Fuentes
2010-08-06 16:33 ` vc-mode-line Óscar Fuentes
2010-08-06 18:12 ` vc-mode-line Eli Zaretskii
2010-08-06 5:12 ` vc-mode-line Miles Bader
2010-08-10 15:29 ` vc-mode-line David House
2010-08-10 15:43 ` vc-mode-line Óscar Fuentes
2010-08-12 13:08 ` vc-mode-line Ted Zlatanov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=buok4o5fyk4.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=dann@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).