unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Leo Liu <sdl.web@gmail.com>, emacs-devel@gnu.org
Subject: Re: Eldoc mode in eval-minibuffer
Date: Mon, 20 Jan 2014 12:59:26 -0500	[thread overview]
Message-ID: <jwvfvoi8rqa.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83bnz6iqtr.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 20 Jan 2014 18:02:56 +0200")

> Besides the usual gripes about such prominent changes in behavior
> being made during feature freeze,

I don't know of such a change.  AFAIK the change to eldoc installed
recently was about changing the implementation of
eldoc-post-insert-mode, to make it more like the normal eldoc mode.
I.e. a change in implementation more than in behavior.

>  . Since it is not in NEWS, chances are it will never get mentioned in
>    the manual, which is bad for default behavior.

IIUC this change in behavior was not intended.

Leo, can you take a look to see what's going on?

>  . 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?

It doesn't.

>    The latter two sound like much better candidates for this feature.

Indeed, I'd like to enable eldoc-mode by default wherever it's
supported, but that's for after 24.4.

>  . 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.

The discussions were about making eldoc work in the minibuffer, not
about enabling it, AFAIK.


        Stefan



  parent reply	other threads:[~2014-01-20 17:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 16:02 Eldoc mode in eval-minibuffer Eli Zaretskii
2014-01-20 17:48 ` 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 [this message]
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=jwvfvoi8rqa.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@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 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).