From: Colin Yates <colin.yates@gmail.com>
To: Emacs Help <help-gnu-emacs@gnu.org>
Subject: org-mode questions
Date: Sun, 23 Aug 2015 01:55:50 +0100 [thread overview]
Message-ID: <m2io86lt61.fsf@gmail.com> (raw)
Hi, (newbie warning)
I am about to embark on some extensive writing (in Markdown) and
org-mode might be just the ticket for this. I particularly like the idea
of narrowing, which I understand the markdown mode doesn't offer.
I envisage my .org file having the following structure:
* resources
* reviews
** review 1
** ...
** review n
* release
** Chapter 1
** ..
** Chapter n
The actual 'contents' being under 'release'.
What I want is to effectively say to org "copy everything under
'release', promote them all to top level headings and then export them
all as markdown.
I can do this manually with killing and yanking, and if I scratch my
head a bit (till it bleeds actually) then I expect I could even do this
in a function.
However, either this is a really common use-case in which I expect I am
missing something in org-mode _or_ this is a weird use-case in which
case I don't want to start and would rather be more idiomatic.
Any thoughts/guidance welcome!
Thanks,
Colin
Sent with my mu4e
next reply other threads:[~2015-08-23 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 0:55 Colin Yates [this message]
2015-08-23 2:07 ` org-mode questions Eric Abrahamsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2io86lt61.fsf@gmail.com \
--to=colin.yates@gmail.com \
--cc=help-gnu-emacs@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.
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).