From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Dan Nicolaescu <dann@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Introduce eldoc support in minibuffer
Date: Sun, 03 Jul 2011 06:55:36 +0200 [thread overview]
Message-ID: <87hb743quv.fsf@gmail.com> (raw)
In-Reply-To: <yxq39iob8q6.fsf@fencepost.gnu.org> (Dan Nicolaescu's message of "Sat, 02 Jul 2011 18:47:45 -0400")
Dan Nicolaescu <dann@gnu.org> writes:
> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>
>> Hi,
>> when editing code in minibuffer (M-:) eldoc is not available.
>> This patch provide this feature.
>> eldoc is displayed in mode-line.
>
> Can the code that displays something in the modeline be used for something else?
Yes, try (eldoc-show-in-mode-line "foo")
> It could be used as a (much more functional) tooltip.
> For example C-s is great, but if one does not read the manual is hard to
> know about all it can do. If we could display little help messages it
> would be easy to teach users about various nice features.
I don't use isearch, so i don't know what to display in mode-line, but i
imagine you can display something useful in mode-line, like a minimal
help depending of the context of your search.
I already use that in some places in ioccur and anything.
You can also in addition of a minimal help in mode-line display a
_full window_ with all the binding of isearch but without quitting isearch
like C-h m does actually.
It's not hard to do, just create a help function for isearch and bind it
in isearch map.
For example:
Try M-x anything-buffer+ then C-c ? to see what i mean.
--
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2011-07-03 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 15:39 Introduce eldoc support in minibuffer Thierry Volpiatto
2011-07-02 18:34 ` Thierry Volpiatto
2011-07-02 22:47 ` Dan Nicolaescu
2011-07-03 4:55 ` Thierry Volpiatto [this message]
2011-07-03 6:03 ` Thierry Volpiatto
2011-07-05 14:41 ` Dan Nicolaescu
2011-07-05 17:51 ` Thierry Volpiatto
2011-07-06 15:25 ` Dan Nicolaescu
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=87hb743quv.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=dann@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 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.