From: zimoun <zimon.toutoune@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 43243@debbugs.gnu.org
Subject: bug#43243: emacs-elfeed-org, mapc: Symbol’s function definition is void
Date: Tue, 29 Sep 2020 21:44:59 +0200 [thread overview]
Message-ID: <86sgb0s6ys.fsf@gmail.com> (raw)
In-Reply-To: <87lfgs310x.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (Giovanni Biscuolo's message of "Tue, 29 Sep 2020 20:12:30 +0200")
Hi,
On Tue, 29 Sep 2020 at 20:12, Giovanni Biscuolo <g@xelera.eu> wrote:
> File mode specification error: (void-function org--check-org-structure-template-alist) [2 times]
> Followed link to /home/giovanni/.dotfolder/emacs/.emacs.d/elfeed.org
> mapc: Symbol’s function definition is void:
> org--check-org-structure-template-alist
Hum? What is your ’~/.emacs.d/init.el’&co.? The issue seems the
loading order. It could happen with lazy eval &co. Well, this ’alist’
is from ’org.el’, so it appears to me a bit weird.
> Tomorrow I'll try to catch what's the conflicting package, now I'm using
> this manifest:
I have noticed that you use ’ghc-pandoc’. Except if you require
“pandoc” as an Haskell library for linking, what you want is probably
the package ’pandoc’ (introduced by e380ef14cf).
All the best,
simon
next prev parent reply other threads:[~2020-09-29 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 14:43 bug#43243: emacs-elfeed-org, mapc: Symbol’s function definition is void Giovanni Biscuolo
2020-09-06 15:45 ` Giovanni Biscuolo
2020-09-28 3:07 ` Maxim Cournoyer
2020-09-28 8:18 ` Giovanni Biscuolo
2020-09-29 13:47 ` Maxim Cournoyer
2020-09-29 18:12 ` Giovanni Biscuolo
2020-09-29 19:44 ` zimoun [this message]
2020-10-02 18:08 ` Giovanni Biscuolo
2020-10-02 19:27 ` Giovanni Biscuolo
2020-10-03 8:11 ` Giovanni Biscuolo
2020-10-03 12:40 ` zimoun
2020-10-04 17:21 ` Giovanni Biscuolo
2020-10-04 17:37 ` Maxim Cournoyer
2020-10-05 12:57 ` Giovanni Biscuolo
2020-10-05 13:45 ` zimoun
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sgb0s6ys.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=43243@debbugs.gnu.org \
--cc=g@xelera.eu \
--cc=maxim.cournoyer@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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).