unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Koning <dk@danielkoning.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 41781@debbugs.gnu.org
Subject: bug#41781: 27.0.91; [PATCH] Eldoc describes the wrong function when reading an expression from the minibuffer
Date: Tue, 23 Jun 2020 11:42:39 -0500	[thread overview]
Message-ID: <m2a70tzqbk.fsf@danielkoning.com> (raw)
In-Reply-To: <jwv5zbh98zv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 23 Jun 2020 10:09:05 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Right now, unless overridden by eshell or another package like it, the
>> minibuffer is always in `minibuffer-inactive-mode',
>
> I don't think that's true in the sense of "you get the behavior of
> minibuffer-inactive-mode" (most importantly you don't get its keymap).
> It may be true in the sense of "that's what `major-mode` says", but
> that's rather irrelevant.

I see your point, but I doubt most users and elisp writers would agree
that it's irrelevant what the value of `major-mode' says in plain
English. We should be able to count on drawing some conclusions from it.

Generally, the use of one major for two very different keymaps and
program states (while circumventing the problems by changing things à la
carte) strikes me as a pattern worth deprecating. But I think we agree
on that.

Daniel





  reply	other threads:[~2020-06-23 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  2:56 bug#41781: 27.0.91; [PATCH] Eldoc describes the wrong function when reading an expression from the minibuffer Daniel Koning
2020-06-20  7:49 ` Eli Zaretskii
2020-06-20 16:51   ` Stefan Monnier
2020-06-23  0:08     ` Daniel Koning
2020-06-23  4:17       ` Stefan Monnier
2020-06-23 13:58         ` Daniel Koning
2020-06-23 14:09           ` Stefan Monnier
2020-06-23 16:42             ` Daniel Koning [this message]
2020-06-23 18:37               ` Stefan Monnier
2020-07-04  7:57       ` Eli Zaretskii
2020-08-05 15:59         ` Lars Ingebrigtsen
2020-08-08  8:09           ` Eli Zaretskii

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=m2a70tzqbk.fsf@danielkoning.com \
    --to=dk@danielkoning.com \
    --cc=41781@debbugs.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).