From: Michael Heerdegen <michael_heerdegen@web.de>
To: Narendra Joshi <narendraj9@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Org-store-link in Gnus summary fails
Date: Sat, 11 Nov 2017 13:36:50 +0100 [thread overview]
Message-ID: <87375lm1p9.fsf@web.de> (raw)
In-Reply-To: <87d14qupn7.fsf@gmail.com> (Narendra Joshi's message of "Fri, 10 Nov 2017 20:50:12 +0530")
Narendra Joshi <narendraj9@gmail.com> writes:
> The strange thing is that if I go and re-evaluate the function
> `org-gnus-store-link', it starts working.
>
> Please help me understand what is happening here.
> > Debugger entered--Lisp error: (invalid-function
> > gnus-summary-article-header)
> > gnus-summary-article-header()
> > org-gnus-store-link()
> > #f(compiled-function (f) #<bytecode 0x174a15d>)(org-gnus-store-link)
> > mapcar(#f(compiled-function (f) #<bytecode 0x174a15d>)
> > (org-rmail-store-link
> > org-mhe-store-link org-irc-store-link org-info-store-link
> > org-gnus-store-link
> > org-docview-store-link org-bibtex-store-link org-bbdb-store-link
> > org-w3m-store-link elfeed-link-store-link))
> > org-store-link(nil)
> > funcall-interactively(org-store-link nil)
> > #<subr call-interactively>(org-store-link nil nil)
> > apply(#<subr call-interactively> org-store-link (nil nil))
> > call-interactively@ido-cr+-record-current-command(#<subr
> > call-interactively> org-store-link nil nil)
> > apply(call-interactively@ido-cr+-record-current-command #<subr
> > call-interactively> (org-store-link nil nil))
> > call-interactively(org-store-link nil nil)
> > command-execute(org-store-link)
This kind of error happens when a file had been compiled without the
according macro definition been loaded.
If just recompiling doesn't help, there is probably a missing dependency
(at compile time).
Michael.
next prev parent reply other threads:[~2017-11-11 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 15:17 Org-store-link in Gnus summary fails Narendra Joshi
2017-11-10 15:20 ` Narendra Joshi
2017-11-11 12:36 ` Michael Heerdegen [this message]
2017-11-11 15:34 ` Narendra Joshi
2017-11-11 17:06 ` Michael Heerdegen
2017-11-11 15:52 ` Eric Abrahamsen
2017-11-11 17:07 ` Michael Heerdegen
2017-11-13 4:05 ` Eric Abrahamsen
2017-11-13 13:13 ` Michael Heerdegen
2017-11-13 15:55 ` Eric Abrahamsen
2017-11-16 23:33 ` Michael Heerdegen
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=87375lm1p9.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=narendraj9@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.
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).