From: Mark Oteiza <mvoteiza@udel.edu>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
28257@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#28257: 26.0.50; [PATCH] expose eldoc functions in a hook
Date: Wed, 26 Jun 2019 10:03:03 -0400 [thread overview]
Message-ID: <20190626140303.quhh4psgvd3aneyr@logos.localdomain> (raw)
In-Reply-To: <87wohasikq.fsf@gmail.com>
On 24/06/19 at 06:51pm, Noam Postavsky wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Mark Oteiza <mvoteiza@udel.edu> writes:
> >
> >>> Could be a worthwhile tradeoff (especially
> >>>since there currently aren't any individual mode eldoc functions using
> >>>anything apart from :before-until, afaik); I'm on the fence about this.
> >>
> >> Not in emacs, at least. In elpa, ggtags uses :after-until. The only
> >> 3rd party packages--that I can think of right now--that implement eldoc
> >> functions just use setq-local (elpy and geiser).
> >
> > Noam, still on the fence?
>
> I haven't really thought about this much, maybe bring it up on
> emacs-devel?
I happily rolled with this patch until some changes to eldoc broke it.
Will post a new patch when I get around to it.
next prev parent reply other threads:[~2019-06-26 14:03 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 [this message]
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
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=20190626140303.quhh4psgvd3aneyr@logos.localdomain \
--to=mvoteiza@udel.edu \
--cc=28257@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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.