From: Ihor Radchenko <yantar92@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Inline src org block element with containing inside item does not get exported when it contains a newline (was: Inline src block element not parsed correctly for export when in a list item)
Date: Wed, 06 Apr 2022 12:22:05 +0800 [thread overview]
Message-ID: <87lewi7seq.fsf@localhost> (raw)
In-Reply-To: <CAFyQvY1OQ-EYzf3kEajHSBU0ewQN5sOmsJtRO3FyV7EgD-5ZZg@mail.gmail.com>
Confirmed.
Interestingly, I cannot reproduce the bug using my personal branch at
https://github.com/yantar92/org. The fix should be lurking somewhere
close...
Kaushal Modi <kaushal.modi@gmail.com> writes:
> I believe I have come across a corner case issue where the inline src
> block element doesn't get parsed as one, if:
The element actually does get parsed. Once can check it by running M-:
(org-element-context) with point at the problematic inline src block.
However, the export is somehow broken.
> * Doesn't export correctly if inline src block is in a wrapped list
> - abcdefg abcdefg abcdefg abcdefg src_org[:exports code]{[[abc
> def][bar]]}.
One observation is that export is again correct if I remove a '[' in the
link inside inline source block.
Best,
Ihor
next prev parent reply other threads:[~2022-04-06 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 3:10 Inline src block element not parsed correctly for export when in a list item Kaushal Modi
2022-03-16 12:47 ` Kaushal Modi
2022-04-06 4:22 ` Ihor Radchenko [this message]
2022-05-14 9:40 ` Inline src org block element with containing inside item does not get exported when it contains a newline (was: Inline src block element not parsed correctly for export when in a list item) Ihor Radchenko
2022-05-16 2:51 ` Kaushal Modi
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=87lewi7seq.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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/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).