From: Kaushal Modi <kaushal.modi@gmail.com>
To: Adam Porter <adam@alphapapa.net>, emacs-org list <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: Sat, 02 Sep 2017 03:01:56 +0000 [thread overview]
Message-ID: <CAFyQvY0boLxELfPjH1KDXrZjV3abQuRXV-=wfbW48Nf1gGge8g@mail.gmail.com> (raw)
In-Reply-To: <878thxhl38.fsf@alphapapa.net>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Fri, Sep 1, 2017, 10:49 PM Adam Porter <adam@alphapapa.net> wrote:
> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> > M-x list-load-path-shadows will also help. Pay attention to shadows on
> org packages.
>
> Wow, I did not know about that command. I have a bit of cleaning-up to
> do. :)
>
That's what I did when I found the shadows too :)
Here's how I make sure no mixed installations happen among Emacs-built-in,
Elpa and git Org versions:
https://scripter.co/building-org-development-version/
In addition to load-path, I also handle Info-path so that the correct Org
manual gets loaded.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1400 bytes --]
next prev parent reply other threads:[~2017-09-02 3:02 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
2017-09-02 2:48 ` Adam Porter
2017-09-02 3:01 ` Kaushal Modi [this message]
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='CAFyQvY0boLxELfPjH1KDXrZjV3abQuRXV-=wfbW48Nf1gGge8g@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
/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.