From: Sam Halliday <sam.halliday@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
Date: Sun, 20 Aug 2017 19:10:13 +0100 [thread overview]
Message-ID: <CALR_T9DxQFB0-oRM+Od68ZTB14T=u1p=Dq47ZQtcg3qFwvSx1A@mail.gmail.com> (raw)
In-Reply-To: <87inhil1lh.fsf@nicolasgoaziou.fr>
On 20 August 2017 at 16:07, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Sam Halliday <sam.halliday@gmail.com> writes:
>
>> To ensure that the Emacs-installed org-mode is not interfering, I
>> added this to my init
>>
>> (cl-delete-if
>> (lambda (el) (string-match-p ".*org" el))
>> load-path)
>>
>> and I can confirm that emacs/org is not in my load-path.
>>
>> However, the backtrace still occurs.
>
> As I wrote, it is still a problem of mixed installation. Quoting the
> manual
>
> Recent Emacs distributions include a packaging system which lets you
> install Elisp libraries. You can install Org with ‘M-x package-install
> RET org’.
>
> Important: you need to do this in a session where no ‘.org’ file has
> been visited, i.e., where no Org built-in function have been loaded.
> Otherwise autoload Org functions will mess up the installation.
>
> Then, to make sure your Org configuration is taken into account,
> initialize the package system with ‘(package-initialize)’ in your
> ‘.emacs’ before setting any Org option. If you want to use Org’s
> package repository, check out the Org ELPA page
> (http://orgmode.org/elpa.html).
Yes, I followed this exactly and the problem still occurs.
If you are confirming that org is definitely compatible with my .org
file then I can try to investigate what could be causing the Emacs org
to load. I cannot see how that is possible since it is not even
available on the elisp path anymore.
Is there a way to check which elisp files have been loaded? Then I can
grep for anything from the emacs org install instead of my local
install.
next prev parent reply other threads:[~2017-08-20 18:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 9:45 Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)] Sam Halliday
2017-08-19 9:50 ` Nicolas Goaziou
2017-08-20 14:47 ` Sam Halliday
2017-08-20 15:07 ` Nicolas Goaziou
2017-08-20 18:10 ` Sam Halliday [this message]
2017-08-20 20:23 ` Nicolas Goaziou
2017-08-21 0:40 ` Kaushal Modi
2017-08-21 17:32 ` Sam Halliday
2017-09-02 2:48 ` Adam Porter
2017-09-02 3:01 ` Kaushal Modi
2017-09-02 3:30 ` Adam Porter
2017-09-04 6:03 ` Loris Bennett
2017-09-04 22:43 ` Adam Porter
2017-09-05 6:21 ` Loris Bennett
2017-09-05 7:41 ` Tim Cross
2017-09-05 8:24 ` Loris Bennett
2017-09-08 10:13 ` Adam Porter
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='CALR_T9DxQFB0-oRM+Od68ZTB14T=u1p=Dq47ZQtcg3qFwvSx1A@mail.gmail.com' \
--to=sam.halliday@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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.