From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Eldoc mode in eval-minibuffer
Date: Mon, 20 Jan 2014 18:02:56 +0200 [thread overview]
Message-ID: <83bnz6iqtr.fsf@gnu.org> (raw)
About a week ago Emacs on trunk started turning on eldoc-mode whenever
you type M-:, with the effect that a large portion of the mode line
gets overwritten "displaced" by information about the forms you type
into the minibuffer.
Besides the usual gripes about such prominent changes in behavior
being made during feature freeze, I have the following complaints:
. This change doesn't seem to be mentioned in NEWS. The closest
thing is this laconic note:
** Eldoc Mode works properly in the minibuffer.
Good luck understanding from this that it is now turned on in the
minibuffer _by_default_. It took me several minutes to figure out
who or what did this to my mode line. Showing this to Emacs users,
let alone newbies, is an excellent candidate for an exam whose
purpose is to detect heirs to Stefan as head maintainer.
. Since it is not in NEWS, chances are it will never get mentioned in
the manual, which is bad for default behavior.
. There doesn't seem to be any way of turning this feature off,
except by setting eldoc-idle-delay to some ridiculously high value.
Consequently, 'customize-changed-options' will not say a word about
this new feature. That's not Emacs'y.
. Why does it make sense to show this information when you eval in
the minibuffer, but not when you eval in *scratch* or in IELM? The
latter two sound like much better candidates for this feature.
. I don't think turning this on by default in eval-minibuffer was
ever seriously discussed. The ChangeLog entry refers to an obscure
bug report, but the discussions of that bug (which I have read at
the time, as I do with all bugs) never explicitly said anything
about the effect I see. Makes me think that perhaps all this is
some mistake or unintentional consequence.
Apologies if I'm missing something obvious.
next reply other threads:[~2014-01-20 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 16:02 Eli Zaretskii [this message]
2014-01-20 17:48 ` Eldoc mode in eval-minibuffer Thierry Volpiatto
2014-01-21 1:23 ` Leo Liu
2014-01-21 1:42 ` Leo Liu
2014-01-21 9:52 ` Thierry Volpiatto
2014-01-21 13:41 ` Stefan Monnier
2014-01-21 13:35 ` Stefan Monnier
2014-01-20 17:59 ` Stefan Monnier
2014-01-20 19:25 ` Eli Zaretskii
2014-01-20 19:47 ` Glenn Morris
2014-01-21 1:32 ` Leo Liu
2014-01-21 2:05 ` Stefan Monnier
2014-01-21 2:24 ` Leo Liu
2014-01-22 10:28 ` Darren Hoo
2014-01-22 13:41 ` Stefan Monnier
2014-01-21 3:45 ` 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=83bnz6iqtr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.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 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).