From: Leo Liu <sdl.web@gmail.com>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Eldoc mode in eval-minibuffer
Date: Tue, 21 Jan 2014 09:23:33 +0800 [thread overview]
Message-ID: <m1fvoi86wa.fsf@gmail.com> (raw)
In-Reply-To: <871u02r1c1.fsf@gmail.com> (Thierry Volpiatto's message of "Mon, 20 Jan 2014 18:48:46 +0100")
On 2014-01-21 01:48 +0800, Thierry Volpiatto wrote:
> BTW This default eldoc in minibuffer is not working properly,
> type e.g "(defun"
> The defun eldoc string is displayed, ok.
> Type <backspace> <backspace>
> you have now "(def"
> in minibuffer but the eldoc string of defun is still present in
> minibuffer, you should have now the default mode-line.
> This bug is fixed in eldoc-eval.el.
>
> And yes this default eldoc in minibuffer is difficult to enable/disable.
> IMO you should have a mode instead to turn this on or off.
>
> See https://github.com/thierryvolpiatto/eldoc-eval
I am not sure what you mean. eldoc should work fine in eval-expression
or more generally in the minibuffer for example I am using it with
erlang eval every day in the past month. If not we should fix it.
Some time ago you posted eldoc-eval and Stefan requested to merge it
with eldoc. None happened. So I picked it up and added this to eldoc.el.
The intention is to make eldoc-eval obsolete.
Leo
next prev parent reply other threads:[~2014-01-21 1:23 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1fvoi86wa.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@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 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.