From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Use of minibuffer-prompt face when minibuffer is not involved
Date: Sat, 11 May 2019 17:11:35 +0300 [thread overview]
Message-ID: <83o949cc88.fsf@gnu.org> (raw)
In-Reply-To: <c7e501bb-9dd8-4b00-8647-d0731f2b2565@default> (message from Drew Adams on Sat, 11 May 2019 06:52:31 -0700 (PDT))
> Date: Sat, 11 May 2019 06:52:31 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: drew.adams@oracle.com, emacs-devel@gnu.org
>
> > Active minibuffer is an internal detail. I wish it didn't exist at
> > all, but our implementation forces us to have it. Exposing that to
> > users is exactly the wrong idea.
>
> Active minibuffer is in _no_ way "an internal detail".
You have 2 core Emacs developers disagree with you, which is a clear
sign that you are wrong.
> "Grave mistake"? Why do you say so? (No reason given.)
I actually did give a reason, please re-read what I wrote.
> We (since Emacs 22, at least) now provide two different
> faces for the mode-line, to show which window is active
> (selected) - which has the focus. This is very similar:
> the minibuffer is a buffer in a window.
No, selected window is an entirely different concept.
> No argument has been given yet supporting _why_ this
> should be considered "internal". Just two opinions
> strongly proclaiming that it _is_ an internal detail.
> Why do you think so?
Read the code, and you will clearly see that.
next prev parent reply other threads:[~2019-05-11 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 18:35 Use of minibuffer-prompt face when minibuffer is not involved Kévin Le Gouguec
2019-05-10 20:52 ` Stefan Monnier
2019-05-10 21:59 ` Drew Adams
2019-05-10 22:36 ` Stefan Monnier
2019-05-11 6:25 ` Eli Zaretskii
2019-05-11 13:22 ` Kévin Le Gouguec
[not found] ` <<jwvftpm9buh.fsf-monnier+emacs@gnu.org>
[not found] ` <<83o949ecdc.fsf@gnu.org>
2019-05-11 13:52 ` Drew Adams
2019-05-11 14:11 ` Eli Zaretskii [this message]
2019-05-12 22:31 ` Richard Stallman
2019-05-12 23:32 ` Drew Adams
[not found] ` <<<jwvftpm9buh.fsf-monnier+emacs@gnu.org>
[not found] ` <<<83o949ecdc.fsf@gnu.org>
[not found] ` <<c7e501bb-9dd8-4b00-8647-d0731f2b2565@default>
[not found] ` <<83o949cc88.fsf@gnu.org>
2019-05-11 14:34 ` Drew Adams
2019-05-11 13:50 ` Solving bug#35564 (was: Use of minibuffer-prompt face when minibuffer is not involved) Kévin Le Gouguec
2019-05-11 14:13 ` Solving bug#35564 Stefan Monnier
[not found] <<8736lmi2dg.fsf@gmail.com>
[not found] <<<8736lmi2dg.fsf@gmail.com>
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=83o949cc88.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).