all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21112@debbugs.gnu.org, Raffaele Ricciardi <rfflrccrd@gmail.com>
Subject: bug#21112: 25; Patch: show minibuffer messages with a face
Date: Thu, 27 Jun 2019 14:37:45 -0700 (PDT)	[thread overview]
Message-ID: <18c4ab5e-277c-4241-86dd-89ca1e870ee7@default> (raw)
In-Reply-To: <87zhm39bu3.fsf@mail.linkov.net>

> Without highlighting of minibuffer messages there is a danger that the
> message will remain unnoticed, especially in the multiline minibuffer.

Danger?  Really?

Some people don't like danger notices.
Some people don't like (what they call) "angry
fruit salad".  Some people don't like lots of
highlighting - or even any highlighting, e.g.
in something like Dired.  Some people even
turn off `font-lock-mode'.

(I'm not one of those people, but they exist.)

People are different.  Their use cases and
contexts of use are different.  One size does
not fit all.

> So minibuffer messages need to be highlighted for the same reason
> why the minibuffer prompt is already highlighted:


"Need to be"?  Neither of those things _needs_
to be highlighted.  Lots of us users will
appreciate that they can be highlighted.

We'll also appreciate being able to choose
how, how much, and whether they're highlighted.

> 1. to designate non-editable read-only parts of the minibuffer;
> 2. to help the users to turn attention to the active part
>    of the minibuffer.

I agree (personally and generally) with those
aids - helpful.  I don't agree about there
being "danger" if they are absent.

> Thus all informational text in the minibuffer should be highlighted
> consistently in one color to help not to miss important message.

"Thus"?  That doesn't follow, even if one accepts
your argument above.  Nothing in that argument
implies that ALL informational text in the
minibuffer should be highlighted CONSISTENTLY IN
ONE COLOR.

It's quite possible for important messages not to
be missed without such a paint-it-all-the-same
approach.  It's quite possible that some code
wants (and the users who choose to use that code
want) to emphasize certain parts of a message
specially - including precisely "to help not to
miss" something particularly noteworthy.

What is true in this regard of `message' is also
true of `minibuffer-message'.  Are you thinking
of imposing the same kind of blanket treatment
for `message'?  If not, why not?  Why doesn't
that apply also to `minibuffer-message'?

> Isn't it so already that elsewhere in Emacs font-lock is used
> to highlight more important parts of the buffer?

Font-lock does not impose a single face
("consistently in one color") for all its
highlighting, does it?  Why not?  Because it
can be useful to emphasize different things
differently...





  reply	other threads:[~2019-06-27 21:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 12:46 bug#21112: 25; Patch: show minibuffer messages with a face Raffaele Ricciardi
2015-07-22 13:42 ` Drew Adams
2015-07-22 13:44   ` Drew Adams
2015-07-22 15:27     ` Raffaele Ricciardi
2015-07-22 15:42       ` Drew Adams
2016-02-23  9:34 ` Lars Ingebrigtsen
2019-06-25 15:50   ` Lars Ingebrigtsen
2019-06-25 19:47     ` Juri Linkov
2019-06-25 20:43       ` Lars Ingebrigtsen
2019-06-26 21:28         ` Juri Linkov
2019-06-27 10:28           ` Lars Ingebrigtsen
2019-06-27 14:22             ` Drew Adams
2019-06-27 20:29               ` Juri Linkov
2019-06-27 21:19                 ` Drew Adams
2019-06-27 20:28             ` Juri Linkov
2019-06-27 21:37               ` Drew Adams [this message]
2019-07-04 22:01         ` Juri Linkov
2019-06-25 20:54       ` Drew Adams
2019-06-26 21:30         ` Juri Linkov
2019-06-26 22:13           ` Drew Adams

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=18c4ab5e-277c-4241-86dd-89ca1e870ee7@default \
    --to=drew.adams@oracle.com \
    --cc=21112@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.org \
    --cc=rfflrccrd@gmail.com \
    /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.