From: Marcin Borkowski <firstname.lastname@example.org>
To: Max Nikulin <email@example.com>
Subject: Re: How to export to markdown programmatically without the table of contents?
Date: Sun, 08 May 2022 08:24:57 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 2022-05-07, at 10:16, Max Nikulin <email@example.com> wrote:
> On 02/05/2022 23:52, Marcin Borkowski wrote:
>> On 2022-05-01, at 22:01, Berry, Charles wrote:
>>>> On May 1, 2022, at 2:20 AM, Marcin Borkowski wrote:
>>>> I'd like to export a Org-mode formatted string to markdown, but without
>>>> the table of contents.
>>>> (org-export-string-as my-string 'md t '(toc nil))
>>>> didn't work (the ToC was still there). What am I missing?
>>> It does seem odd that BODY-ONLY as `t' gives a toc. With latex it does not regardless of `:with-toc'.
>>> : (org-export-string-as my-string 'md t '(:with-toc nil))
> The following links posted earlier to this mail list might be
> interesting for you since they are related to "exporting" of org text
> to other applications:
> System-wide popup Emacs windows for quick edits
> Copy formatted content from org-mode
> The latter copies HTML, not markdown though.
Thanks, both look really interesting!
prev parent reply other threads:[~2022-05-08 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 9:20 How to export to markdown programmatically without the table of contents? Marcin Borkowski
2022-05-01 19:59 ` Jeremie Juste
2022-05-01 20:01 ` Berry, Charles
2022-05-01 20:29 ` Jeremie Juste
2022-05-02 6:06 ` Daniel Fleischer
2022-05-02 16:52 ` Marcin Borkowski
2022-05-03 9:15 ` Karl Voit
2022-05-03 21:02 ` Jeremie Juste
2022-05-04 11:45 ` Karl Voit
2022-05-04 4:13 ` Daniel Fleischer
2022-05-07 8:16 ` Max Nikulin
2022-05-08 6:24 ` Marcin Borkowski [this message]
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 \
* 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).