unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel <emacs-devel@gnu.org>, emacspeak@emacspeak.org
Subject: Re: eldoc errors in elisp
Date: Sun, 23 Apr 2023 11:28:48 +0100	[thread overview]
Message-ID: <CALDnm52PeM-nZ=Qiy+mK8b_H1HPRO4YAnesaR+6ppu2y2OgZ6A@mail.gmail.com> (raw)
In-Reply-To: <25668.39773.281157.196963@retriever.mtv.corp.google.com>

[-- Attachment #1: Type: text/plain, Size: 582 bytes --]

On Sun, Apr 23, 2023, 03:43 T.V Raman <raman@google.com> wrote:

> Awesome, will rewrite once I hear back.
>
> One constraint -- I'd like to keep backwrd compatibility with Emacs 28
> since Emacs 29 is not yet ready for release.
>
> I myself run Emacs from Git@Head
>

Yes. All three versions will work consistently if you apply the technique
of using the arguments passed to your custom member of the
eldoc-display-functions hook instead of consulting the internal variable.

IOW the latest refactoring in ElDoc  was done in a backward-compatible way.

João

>

[-- Attachment #2: Type: text/html, Size: 1156 bytes --]

  reply	other threads:[~2023-04-23 10:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22 15:33 eldoc errors in elisp T.V Raman
2023-04-22 16:20 ` João Távora
2023-04-22 16:37   ` T.V Raman
2023-04-22 17:45     ` João Távora
2023-04-22 18:13       ` T.V Raman via Emacspeak
2023-04-22 21:25         ` João Távora
2023-04-23  2:43           ` T.V Raman via Emacspeak
2023-04-23 10:28             ` João Távora [this message]
2023-04-23 12:14               ` João Távora
2023-04-23 14:26               ` T.V Raman via Emacspeak
2023-04-23 14:35                 ` João Távora

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALDnm52PeM-nZ=Qiy+mK8b_H1HPRO4YAnesaR+6ppu2y2OgZ6A@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacspeak@emacspeak.org \
    --cc=raman@google.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).