From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Q: ox-md does not translate link searches to #bookmarks in markdown [9.4.4 (release_9.4.4 @ /snap/emacs/current/usr/share/emacs/27.2/lisp/org/)]
Date: Wed, 12 May 2021 15:05:20 +1000 [thread overview]
Message-ID: <87cztwbknu.fsf@gmail.com> (raw)
In-Reply-To: <CAAhEMb94YT7L=QHL+8MNCeMonznoK3ath+Y0XgpqMUXb=FbOCA@mail.gmail.com>
Phil Marneweck <haragx@gmail.com> writes:
> Hi
>
> Is this by design?
>
> I expected to following
>
> [[file:some-file.org::#some-heading][some text]]
>
> to translate to this
>
> [some text](some-file.md#some-heading)
>
> So in org-md-link I would have thought that the default would be more like this
>
> (t (if (not desc) (format "<%s>" path)
> (format "[%s](%s%s)" desc path (or (org-element-property :search-option link) ""))))
>
> You would of course have to do some sanity checking on search-option to just take care of id versus headline searches etc.
>
I'm not sure if this is by design or because of limitations in the
markdown dialect used by org mode (see
http://daringfireball.net/projects/markdown) or just a bug. My
suspicion, after a quick review of the markdown syntax on the
daringfireball site is that search links are not supported.
This is one of those examples of the problems arising from a format type
which does not have a specification. There are numerous different
markdown dialects and org had to select one. Problem is, everyone gets
use to a particular dialect and then is often disappointed when org's
dialect does not match their expectations. One reason we also have the
github flavoured markdown exporter.
--
Tim Cross
prev parent reply other threads:[~2021-05-12 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 15:26 Q: ox-md does not translate link searches to #bookmarks in markdown [9.4.4 (release_9.4.4 @ /snap/emacs/current/usr/share/emacs/27.2/lisp/org/)] Phil Marneweck
2021-05-12 5:05 ` Tim Cross [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:
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=87cztwbknu.fsf@gmail.com \
--to=theophilusx@gmail.com \
--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 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).