From: martin rudalics <rudalics@gmx.at>
To: "T.V Raman" <raman@google.com>, emacs-devel@gnu.org
Subject: Re: eldoc broken?
Date: Fri, 9 Apr 2021 16:54:32 +0200 [thread overview]
Message-ID: <866e96a8-a188-4973-4bce-2aca742d5b4d@gmx.at> (raw)
In-Reply-To: <24684.57027.135326.658583@google.com>
> (funcall eldoc-documentation-function)
> eventually leads to an error
> --- backtrace below
>
> because eldoc sets
> (defvar eldoc--make-callback nil "Helper for function
> `eldoc--make-callback'.")
> as far as I can tell, the defvar above never receives a function
> assigned to it.
>
>
> Symbol’s function definition is void: nil
See Bug#43609.
martin
prev parent reply other threads:[~2021-04-09 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 22:20 eldoc broken? T.V Raman
2021-04-09 14:54 ` martin rudalics [this message]
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=866e96a8-a188-4973-4bce-2aca742d5b4d@gmx.at \
--to=rudalics@gmx.at \
--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 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).