On Wed, Aug 23, 2017 at 4:55 PM, Kaushal Modi
wrote:
> On Tue, Aug 22, 2017 at 4:10 PM Matt Price wrote:
>
>> And then I'd run some elisp that mashes them all up together, and give
>> that to the students, since I think that'll make it easier for them to read.
>>
>> Anyone on the list have any i
On Tue, Aug 22, 2017 at 4:10 PM Matt Price wrote:
> And then I'd run some elisp that mashes them all up together, and give
> that to the students, since I think that'll make it easier for them to read.
>
> Anyone on the list have any ideas?
>
How about using plain old #+INCLUDE:
Example made up
Hi Matt,
One potentially crazy idea would be to store each lab/discussion entry
in a named "#+BEGIN_SRC org" block, and use Babel <> 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 po
I maintain syllabi for courses htat have *discussion* ocmponents and *lab*
ocmponents; these are often quite separate from one another.
I end up with trees that look like this:
* Outline
** <2017-09-12 Tue> (Week {{{n}}}) Hacking History in the Himalaya
Why we should write history, why everyone
