From: "João Távora" <joaotavora@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: Need help with eldoc:
Date: Fri, 25 Mar 2022 22:52:45 +0000 [thread overview]
Message-ID: <87y20xd4qq.fsf@gmail.com> (raw)
In-Reply-To: <25149.52138.240688.137767@retriever.mtv.corp.google.com> (T. V. Raman's message of "Fri, 25 Mar 2022 07:03:22 -0700")
"T.V Raman" <raman@google.com> writes:
> This is awesome!
>
> Q: what is "patch in PS"?
"patch in Post Scriptum" means I attached a small diff at the end of the
email, after my signature. This will repurpose the eldoc-doc-buffer
function for non-interactive use, as we discussed.
> Once you push the patch to emacs git I'll implement what you suggest
> as the final solution.
OK. Perfect. For now you can use one of the solutions using internal
symbols. I believe they are unlikely to change in the near future.
> One more question -- Once I have this working well for myself, I then
> need to build a solution that works when Emacs 28 releases --- since I
> cant depend on all emacspeak users running emacs from @HEAD, but I'd
> like to first get the *final* solution right, then worry about
> backwards compat.
Actually, this _might_ be a non-problem. You see, eldoc.el is a GNU
ELPA "core package" that works in older versions of Emacs as long as
they're >= 26.3. You can see this in the header of the eldoc.el file:
;; Package-Requires: ((emacs "26.3"))
;; This is a GNU ELPA :core package. Avoid functionality that is not
;; compatible with the version of Emacs recorded above.
So if you can arrange for emacsspeak to either use package.el ELPA
packages or simply for emacsspeak to load the Emacs's
lisp/emacs-lisp/eldoc.el file, then "you're golden", as they say.
João
next prev parent reply other threads:[~2022-03-25 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 14:21 Need help with eldoc: T.V Raman
2022-03-24 23:28 ` João Távora
2022-03-24 23:39 ` T.V Raman
2022-03-25 0:16 ` João Távora
2022-03-25 2:21 ` T.V Raman
2022-03-25 10:03 ` João Távora
2022-03-25 14:03 ` T.V Raman
2022-03-25 22:52 ` João Távora [this message]
2022-03-25 14:27 ` T.V Raman
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=87y20xd4qq.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.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 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.