From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 19696@debbugs.gnu.org, Fabian Ezequiel Gallina <galli.87@gmail.com>
Subject: bug#19696: Acknowledgement (24.4; python.el: blank line eldoc error)
Date: Wed, 04 Feb 2015 13:35:12 -0500 [thread overview]
Message-ID: <jwv61bh8r4w.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAELgYhcCUOy=wCzy5zP3+4qLUxaxhS_7neuQ2NV+KA90LVWDXw@mail.gmail.com> (Carlos Pita's message of "Wed, 4 Feb 2015 15:11:38 -0300")
> I'm not the expert here, but could it be that there is no previous
> value for eldoc-documentation-function?
eldoc-documentation-function is defined in eldoc.el as:
(defvar eldoc-documentation-function #'ignore
...)
and eldoc.el is preloaded, so the var should not be nil.
Which version of Emacs is that? Your report seems to say Emacs-24.4,
but the add-function call in python.el is new in master, AFAICT.
Are you by any chance using the python.el from master with an
older Emacs?
Stefan
next prev parent reply other threads:[~2015-02-04 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 17:32 bug#19696: 24.4; python.el: blank line eldoc error Carlos Pita
[not found] ` <handler.19696.B.14222935664090.ack@debbugs.gnu.org>
2015-02-03 23:23 ` bug#19696: Acknowledgement (24.4; python.el: blank line eldoc error) Carlos Pita
2015-02-04 15:25 ` Stefan Monnier
2015-02-04 18:01 ` Carlos Pita
2015-02-04 18:11 ` Carlos Pita
2015-02-04 18:35 ` Stefan Monnier [this message]
2015-02-04 18:43 ` Carlos Pita
2015-02-04 18:59 ` Carlos Pita
2015-02-04 19:34 ` Stefan Monnier
2015-02-04 19:47 ` Carlos Pita
2015-02-04 22:38 ` Fabián Ezequiel Gallina
2015-02-05 2:47 ` Stefan Monnier
2015-02-05 9:09 ` Fabián Ezequiel Gallina
2015-02-09 15:56 ` bug#19696: python.el: blank line eldoc error Carlos Pita
2015-02-10 2:54 ` Fabián Ezequiel Gallina
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=jwv61bh8r4w.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19696@debbugs.gnu.org \
--cc=carlosjosepita@gmail.com \
--cc=galli.87@gmail.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.