From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, npostavs@users.sourceforge.net,
npostavs@gmail.com, monnier@iro.umontreal.ca,
28257@debbugs.gnu.org
Subject: bug#28257: 26.0.50; [PATCH] expose eldoc functions in a hook
Date: Tue, 25 Feb 2020 18:18:33 -0500 [thread overview]
Message-ID: <20200225231833.GA25695@holos.localdomain> (raw)
In-Reply-To: <83lfowjpia.fsf@gnu.org>
On 21/02/20 at 10:47am, Eli Zaretskii wrote:
> > Date: Fri, 14 Feb 2020 17:54:15 -0500
> > From: Mark Oteiza <mvoteiza@udel.edu>
> > Cc: Lars Ingebrigtsen <larsi@gnus.org>, npostavs@users.sourceforge.net,
> > Noam Postavsky <npostavs@gmail.com>, 28257@debbugs.gnu.org
> >
> > Thanks Noam and Stefan for the catches. New patch below.
>
> Any further comments?
>
> I only spotted an occasional single space between sentences in doc
> strings, but have nothing else? If there are no further comments, I'd
> like to install this.
>
> Thanks.
Pushed as c0fcbd2c119, hopefully adding the missing spaces, and adding
:version and a null option to the type of 'eldoc-documentation-function'
next prev parent reply other threads:[~2020-02-25 23:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 2:10 bug#28257: 26.0.50; [PATCH] expose eldoc functions in a hook Mark Oteiza
2017-08-28 2:49 ` npostavs
2017-08-28 3:11 ` Mark Oteiza
2017-08-29 1:05 ` npostavs
2017-08-30 1:50 ` Mark Oteiza
2019-06-24 16:16 ` Lars Ingebrigtsen
2019-06-24 22:51 ` Noam Postavsky
2019-06-26 14:03 ` Mark Oteiza
2020-01-26 23:47 ` Mark Oteiza
2020-01-31 14:05 ` Eli Zaretskii
2020-02-08 10:03 ` Eli Zaretskii
2020-02-11 21:57 ` Noam Postavsky
2020-02-14 9:58 ` Eli Zaretskii
2020-02-14 14:51 ` Stefan Monnier
2020-02-14 14:50 ` Stefan Monnier
2020-02-14 22:54 ` Mark Oteiza
2020-02-21 8:47 ` Eli Zaretskii
2020-02-25 23:18 ` Mark Oteiza [this message]
2020-08-10 14:42 ` Lars Ingebrigtsen
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=20200225231833.GA25695@holos.localdomain \
--to=mvoteiza@udel.edu \
--cc=28257@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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.