From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [PATCH v3] RFC: eldoc-documentation-functions hook
Date: Thu, 7 Jul 2016 10:55:28 -0400 [thread overview]
Message-ID: <577E6D60.7060908@gmail.com> (raw)
In-Reply-To: <20160707033019.GA22360@holos.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 308 bytes --]
Hi Mark,
On 2016-07-06 23:30, Mark Oteiza wrote:
> Applied with some wording changes as 5811404
Can you clarify why a hook is better than a function? Also, what's the expected transition path? Will all major modes that use eldoc-documentation-function need to be updated at some point?
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-07-07 14:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 6:12 [PATCH] RFC: eldoc-documentation-functions hook Mark Oteiza
2016-06-12 7:09 ` Eli Zaretskii
2016-06-12 7:46 ` Leo Liu
2016-06-12 8:33 ` Eli Zaretskii
2016-06-12 18:24 ` Mark Oteiza
2016-06-13 21:17 ` Mark Oteiza
2016-06-17 21:08 ` [PATCH v3] " Mark Oteiza
2016-07-07 3:30 ` Mark Oteiza
2016-07-07 4:12 ` Leo Liu
2016-07-07 10:02 ` Kaushal Modi
2016-07-17 15:17 ` Noam Postavsky
2016-07-17 17:48 ` Mark Oteiza
2016-07-17 23:47 ` Dmitry Gutov
2016-07-18 0:09 ` Leo Liu
2016-07-17 18:28 ` Stefan Monnier
2016-07-17 18:52 ` Stefan Monnier
2016-07-18 21:27 ` Mark Oteiza
2016-07-19 2:47 ` Stefan Monnier
2016-07-19 23:20 ` Mark Oteiza
2016-07-20 1:50 ` Clément Pit--Claudel
2016-07-20 4:50 ` John Wiegley
2016-07-20 23:03 ` Mark Oteiza
2016-07-07 14:55 ` Clément Pit--Claudel [this message]
2016-06-12 13:23 ` [PATCH] " Noam Postavsky
2016-06-12 18:52 ` Mark Oteiza
2016-06-12 18:57 ` Dmitry Gutov
2016-06-12 19:44 ` Mark Oteiza
2016-06-12 19:50 ` Dmitry Gutov
2016-06-13 20:36 ` Richard Stallman
2016-06-19 2:45 ` Dmitry Gutov
2016-06-20 23:00 ` Richard Stallman
2016-06-13 4:37 ` Leo Liu
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=577E6D60.7060908@gmail.com \
--to=clement.pit@gmail.com \
--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.