From: Mirko Vukovic <mirko.vukovic@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: suggestion for the manual: mention the "#+BEGIN_SRC org" trick when describing drawers and plainlists
Date: Sat, 10 Mar 2012 15:01:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20120310T155254-758@post.gmane.org> (raw)
In-Reply-To: CACfYvRaR9ZusQjnvE3DjPPR+e-611cUWd8A+O_6NwZ4Vj7g-fw@mail.gmail.com
Ilya Shlyakhter <ilya_shl <at> alum.mit.edu> writes:
>
> In Org, entry text can't have substructure (other than drawers and plain
lists): you can't have an entry thathas some text, then a subtree, then more
text.I just (re-)discovered that you can get around that by using "#+BEGIN_SRC
org" to include arbitrary org
> subtrees in the middle of entry text. That's useful not just when writing in
Org about Org, but anytime you wantto insert an extended sidenote in the middle
of an entry. As with all source blocks, you edit it in its native (Org)
> mode and it exports correctly. You can copy links from the main Org and past
them into the nested Org.Just wish I'd learned this sooner :) So, maybe mention
this in the manual in the sections on drawers and plainlists.ilya
Thank you for the pointer. I am sometimes also frustrated by that feature.
But using BEGIN/END_SRC is really a hack. I wonder if instead of using SRC
blocks, we could define (with some amount of coding) a more suitable kind of
blocks. In my case I would like to have a BEGIN/END_TODO block. This would
permit a layout such as
* header 1
text, more text, much more text under header
#+begin_todo
** TODO task
** TODO another task
#+end_todo
still more text under header 1
Maybe the TODO block is to specific. Maybe a SUBTREE block would be sufficient.
Though, I am not sure if this would conflict with some major undrlying structure
of orgmode.
Mirko
next prev parent reply other threads:[~2012-03-10 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 1:13 suggestion for the manual: mention the "#+BEGIN_SRC org" trick when describing drawers and plainlists Ilya Shlyakhter
2012-03-08 1:58 ` Ilya Shlyakhter
2012-03-08 13:14 ` Eric Schulte
2012-03-08 7:32 ` Sebastien Vauban
2012-03-08 12:53 ` Ilya Shlyakhter
2012-03-08 12:59 ` Ilya Shlyakhter
2012-03-10 15:01 ` Mirko Vukovic [this message]
2012-03-10 19:00 ` suvayu ali
2012-03-10 19:47 ` Mirko Vukovic
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=loom.20120310T155254-758@post.gmane.org \
--to=mirko.vukovic@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).