emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sam Halliday <sam.halliday@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
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: Mon, 21 Aug 2017 18:32:41 +0100	[thread overview]
Message-ID: <CALR_T9AWOTAtw0_fm-sjgMSBsaegdWeNevTi0dKt_Fuuk1hDAg@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY2n6d1bkbDWm+L1ZkhV9rvooCvWp9NcMz8OiEQLyS8LNg@mail.gmail.com>

By running this

  (cl-delete-if
   (lambda (el) (string-match-p "/usr/share/.*org" el))
   load-path)

I'm able to hide org and now the org-plus-contrib loads up, yay!
Thanks for the hints.



On 21 August 2017 at 01:40, Kaushal Modi <kaushal.modi@gmail.com> wrote:
> On Sun, Aug 20, 2017, 4:25 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
> wrote:
>>
>>
>> > 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.
>>
>> `locate-library' may help. Also, `load-path' can give a clue. Try with
>> a bare configuration, i.e., with just
>>
>>   (require 'package)
>>   (package-initialize)
>>
>> It can be tricky to find out what is loading bundled Org too early.
>> Enjoy the Frankenorg.
>
>
> :)
>
> M-x list-load-path-shadows will also help. Pay attention to shadows on org
> packages.
>
> --
>
> Kaushal Modi

  reply	other threads:[~2017-08-21 17:32 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
2017-08-20 20:23         ` Nicolas Goaziou
2017-08-21  0:40           ` Kaushal Modi
2017-08-21 17:32             ` Sam Halliday [this message]
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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALR_T9AWOTAtw0_fm-sjgMSBsaegdWeNevTi0dKt_Fuuk1hDAg@mail.gmail.com \
    --to=sam.halliday@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).