From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 49844@debbugs.gnu.org, larsi@gnus.org
Subject: bug#49844: Highlight non-selected minibuffer prompt
Date: Thu, 05 Aug 2021 08:53:46 +0300 [thread overview]
Message-ID: <83v94kjv2t.fsf@gnu.org> (raw)
In-Reply-To: <87pmus27zg.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 05 Aug 2021 00:32:19 +0300)
> From: Juri Linkov <juri@linkov.net>
> Date: Thu, 05 Aug 2021 00:32:19 +0300
> Cc: 49844@debbugs.gnu.org
>
> > Can't we just put it in minibuffer.el? (But then there should probably
> > be a user option to switch it on/off.)
>
> Ironically, minibuffer.el is intended for code that deals with
> completions. Its first line is
>
> ;;; minibuffer.el --- Minibuffer completion functions
That's not carved in stone, though. We could change that heading
accordingly, and start adding stuff to minibuffer.el that doesn't
necessarily deal with completion.
> But most code that deals with the minibuffer
> is somewhere in the middle of simple.el.
Which is somewhat sub-optimal, I think.
> Maybe it would make sense to create a new file with the name e.g.
> minibuf-x.el as a mixed bag of tiny minibuffer features?
I don't think a new file is justified at this time.
next prev parent reply other threads:[~2021-08-05 5:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 7:47 bug#49844: Highlight non-selected minibuffer prompt Juri Linkov
2021-08-04 7:42 ` Lars Ingebrigtsen
2021-08-04 8:41 ` Juri Linkov
2021-08-04 8:53 ` Lars Ingebrigtsen
2021-08-04 21:32 ` Juri Linkov
2021-08-05 5:53 ` Eli Zaretskii [this message]
2021-08-05 11:00 ` Lars Ingebrigtsen
2021-11-06 2:41 ` Lars Ingebrigtsen
2021-11-06 2:42 ` Lars Ingebrigtsen
2021-11-06 18:43 ` Juri Linkov
2021-11-06 21:14 ` Lars Ingebrigtsen
2021-11-07 17:31 ` Juri Linkov
2022-08-22 11:04 ` Lars Ingebrigtsen
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=83v94kjv2t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49844@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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 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.