From: Dmitry Gutov <dmitry@gutov.dev>
To: Juri Linkov <juri@linkov.net>
Cc: 66464@debbugs.gnu.org
Subject: bug#66464: Vc mode-line
Date: Sun, 12 Nov 2023 00:05:32 +0200 [thread overview]
Message-ID: <9b794172-efaa-85d3-ff56-fcd4ecd9e46c@gutov.dev> (raw)
In-Reply-To: <86r0kw3z67.fsf@mail.linkov.net>
On 11/11/2023 20:50, Juri Linkov wrote:
> Currently the options are aligned and provide a nice review
> what the user will see on the mode line:
>
> :type '(choice (const :tag "Show project name and status" with-project)
> (const :tag "Show backend and status" t)
> (const :tag "Show only backend name" nil))
>
> So I'd rather like to describe more details in the docstring.
I don't like the semantics of this sentence (it implies that VC's mode
line item will show the project name but it doesn't), but I'm not going
to argue more.
> Probably it should be sufficient to describe this in the docstring
> like in this patch?
It's good, thank you.
> PS: Probably we could also add another option `no-backend'
> that will show only an indicator and the branch name.
> But the dangling indicator such as "-" or "*" before the branch name
> doesn't look nice when there is a space that separates it
> from the project name, e.g. "project -branch".
It would probably make more sense to me, but having both might be overkill.
FWIW, with the custom mode-line that I use (smart-mode-line) the results
of these two options would look the same -- space-separated anyway.
next prev parent reply other threads:[~2023-11-11 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 16:29 bug#66464: Vc mode-line Juri Linkov
2023-10-16 1:11 ` Dmitry Gutov
2023-10-16 17:14 ` Juri Linkov
2023-10-31 7:40 ` Juri Linkov
2023-11-09 16:41 ` Juri Linkov
2023-11-10 2:04 ` Dmitry Gutov
2023-11-10 7:33 ` Juri Linkov
2023-11-10 23:54 ` Dmitry Gutov
2023-11-11 18:50 ` Juri Linkov
2023-11-11 22:05 ` Dmitry Gutov [this message]
2023-11-12 8:07 ` Juri Linkov
2023-11-12 10:59 ` Dmitry Gutov
2023-11-13 7:11 ` Juri Linkov
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=9b794172-efaa-85d3-ff56-fcd4ecd9e46c@gutov.dev \
--to=dmitry@gutov.dev \
--cc=66464@debbugs.gnu.org \
--cc=juri@linkov.net \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.