emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Cash Weaver <cashbweaver@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Bug with exporting list with link item containing "::" to markdown
Date: Wed, 23 Feb 2022 23:59:07 +0700	[thread overview]
Message-ID: <164e193c-4b7d-398a-2375-622a9b42c048@gmail.com> (raw)
In-Reply-To: <CABGRHLkLGXYgGNm4CXK_LjOTGTpsLO=5aWD=FyPd1aMy2QdBxw@mail.gmail.com>

On 13/02/2022 03:12, Cash Weaver wrote:
> As a quick summary: The following list item is improperly exported to 
> org mode (org-md-export-as-markdown). The first snippet is in org-mode 
> and the second is the exported markdown:
> - [[id:c89158fd-05ac-4c66-8986-05753e15096c][ryans01 :: No Zero Days]]
> - [[id:92cf48f0-63a6-4d1d-9275-c80f6743ccb9][Do Things that Compound]]
> -   **[[<ryans01NoZeroDays2013.md>][ryans01:** No Zero Days]]
> -   [Do Things that Compound](do_things_that_compound.md)

I am marking this issue as a bug for https://updates.orgmode.org/ but it 
may be just non-intuitive behavior of org-element parser. "::" inside an 
item forces the list to be considered as descriptive one. Element which 
parsing started earlier has higher priority. See the following recent 
thread for similar issues:

Juan Manuel Macías. Pandoc and nested emhases.
Fri, 18 Feb 2022 00:47:18 +0000.

You may add zero-width space between colons, see
info "(org) Escape Character" 
https://orgmode.org/manual/Escape-Character.html but it may require 
post-processing filter to remove zero-width spaces.

Another approach is to insert an export snippet:

- [[id:cbce567a-861c-4d9b-8b2f-5933afadb864][ryans01 :@@org:@@: No Zero 

      parent reply	other threads:[~2022-02-23 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 20:12 Bug with exporting list with link item containing "::" to markdown Cash Weaver
2022-02-13  9:13 ` Jeremie Juste
2022-02-13 14:09   ` Kaushal Modi
2022-02-23 16:59 ` Max Nikulin [this message]

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:

  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=164e193c-4b7d-398a-2375-622a9b42c048@gmail.com \
    --to=manikulin@gmail.com \
    --cc=cashbweaver@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).