From: Jeremie Juste <jeremiejuste@gmail.com>
To: Jack Kamm <jackkamm@tatersworld.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Folding problem with markdown source block
Date: Sun, 07 Aug 2022 11:07:21 +0200 [thread overview]
Message-ID: <878ro0mng6.fsf@gmail.com> (raw)
In-Reply-To: <87zgghrsd2.fsf@gmail.com> (Jack Kamm's message of "Sat, 06 Aug 2022 14:10:01 -0700")
Hello Jack,
Thanks for reporting. I can reproduce the bug.
Best regards,
Jeremie
On Saturday, 6 Aug 2022 at 14:10, Jack Kamm wrote:
> Hello,
>
> I found that Org entries containing markdown source blocks don't get
> properly folded on the main development branch, when markdown-mode is
> also loaded.
>
> To reproduce:
>
> 1. Download markdown-mode from MELPA or Github. [1]
> 2. Fix the paths in the attached init.el.
> 3. emacs -Q -l init.el test.org
> 4. Shift-tab to collapse the visibility
>
> Output should look like this:
>
> * Headline 1...
>
> But instead I observe this:
>
> * Headline 1... ```
> ... ```
> ...
>
> If markdown-mode isn't loaded, then the problem goes away. I think the
> problem might have to do with the fontification that markdown-mode
> applies to the back-quoted code block.
>
> Versions:
> GNU Emacs 28.1 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.6, Xaw3d scroll bars) of 2022-07-10
> Org mode version 9.5.4 (release_9.5.4-717-g9cc60d @ /home/jack/dev/org-mode/lisp/)
>
> [1] https://github.com/jrblevin/markdown-mode
>
>
> (add-to-list 'load-path "~/.emacs.d/elpa/markdown-mode-20220708.6")
> (require 'markdown-mode)
>
> (add-to-list 'load-path "~/dev/org-mode/lisp")
>
>
> * Headline 1
> ** Headline 1a
>
> #+begin_src markdown
> Some source code:
>
> ```
> echo hello world
> ```
>
> A list:
>
> ,* Item 1
> ,* Item 2
> #+end_src
>
> ** Headline 1b
>
> Lorem ipsum.
next prev parent reply other threads:[~2022-08-07 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 21:10 Bug: Folding problem with markdown source block Jack Kamm
2022-08-07 9:07 ` Jeremie Juste [this message]
2022-08-07 10:38 ` Ihor Radchenko
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=878ro0mng6.fsf@gmail.com \
--to=jeremiejuste@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@tatersworld.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.