From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 12840@debbugs.gnu.org
Subject: bug#12840: 24.2.50; ediff: mode-line of control buffer - improvement request
Date: Tue, 10 May 2022 14:08:57 +0200 [thread overview]
Message-ID: <875ymdk2sm.fsf@gnus.org> (raw)
In-Reply-To: <87mwys0zrv.fsf@web.de> (Michael Heerdegen's message of "Thu, 08 Nov 2012 18:29:08 +0100")
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Michael Heerdegen <michael_heerdegen@web.de> writes:
> 1. It would be much more convenient if the "diff ... of ..." part would
> be highlighted somehow, so that it is more visible. It is an extremely
> relevant information, and can now be recognized very badly.
>
> The function to change would probably be
> `ediff-make-wide-control-buffer-id'. I tested with this, for example:
[...]
> 'face 'mode-line-buffer-id))))
I wouldn't mind making that bit bold, but it is somewhat unusual for
modes to do that. On the other and, there isn't really a lot of other
info in that mode line, so it wouldn't be distracting, either:
[-- Attachment #2: Type: image/png, Size: 12938 bytes --]
[-- Attachment #3: Type: text/plain, Size: 486 bytes --]
> 2. What's the "Quick Help" part for? I don't see any use for it. It
> seems to be always present, but it doesn't indicate anything, and I
> cannot click on it. Also, if I didn't hit ? in the control buffer, the
> only content of this buffer already is "Type ? for help".
The "Quick Help" bit has a popup that says what mouse-2 and mouse-3
does, which seems somewhat helpful.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-10 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 17:29 bug#12840: 24.2.50; ediff: mode-line of control buffer - improvement request Michael Heerdegen
2022-05-10 12:08 ` Lars Ingebrigtsen [this message]
2022-05-11 0:02 ` Michael Heerdegen
2022-05-11 11:51 ` Lars Ingebrigtsen
2022-06-13 13:50 ` Lars Ingebrigtsen
2022-06-14 14:45 ` Michael Heerdegen
2022-06-15 12:09 ` Lars Ingebrigtsen
2022-06-19 12:30 ` Michael Heerdegen
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=875ymdk2sm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=12840@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).