From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: merging subtrees (in a syllabus)
Date: Wed, 23 Aug 2017 01:25:25 -0500 [thread overview]
Message-ID: <87tw0ykdgq.fsf@alphapapa.net> (raw)
In-Reply-To: CAN_Dec8k_unO+znHq3iUfwpMKZ0wp3FEjA7qUw3Y9tN9zjqnJA@mail.gmail.com
Hi Matt,
One potentially crazy idea would be to store each lab/discussion entry
in a named "#+BEGIN_SRC org" block, and use Babel <<anchors>> to merge
them in a final noweb SRC block. Seems a bit recursive, but I guess you
could edit each org block with org-edit-special and escape the nesting.
Another possibility would be to leave them as they are now, but to use
sparse trees in combination with tags or properties to only display lab
or discussion entries.
Also, you may find org-tree-to-indirect-buffer useful. I have the
impression that not many Org users are aware of it or how
powerful--might I even say, liberating--it is. You can essentially edit
each subtree of your document as a separate document in its own buffer,
while behind the scenes it's all taking place in the source buffer. If
you're interested in this, I could provide some more details and some
support functions that make it more useful.
> If it also comes with a thought about how to generate an org date
> objet form an initial seed and a session number, that's be fabulous
> too.
I just discovered this yesterday, and it seems relevant:
https://github.com/abo-abo/tiny
Apparently it can be used like this:
m\n8|**** TODO Learning from Data Week %(+ x 2) \nSCHEDULED: <%(date "Oct 7" (* x 7))> DEADLINE: <%(date "Oct 14" (* x 7))>
Which results in:
**** TODO Learning from Data Week 2
SCHEDULED: <2013-10-07 Mon> DEADLINE: <2013-10-14 Mon>
**** TODO Learning from Data Week 3
SCHEDULED: <2013-10-14 Mon> DEADLINE: <2013-10-21 Mon>
[...]
Hope this helps!
Adam
next prev parent reply other threads:[~2017-08-23 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 20:09 merging subtrees (in a syllabus) Matt Price
2017-08-23 6:25 ` Adam Porter [this message]
2017-08-23 20:55 ` Kaushal Modi
2017-08-24 0:55 ` Matt Price
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=87tw0ykdgq.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--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).