emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: "Allen S. Rout" <asr@ufl.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: back matter in Org documents.
Date: Thu, 18 Aug 2016 18:10:45 -0400	[thread overview]
Message-ID: <m2h9ahiv8a.fsf@Johns-MacBook-Air.local> (raw)
In-Reply-To: <np58ec$j9b$1@blaine.gmane.org>

you could do something like [[attachfile:./2004-01-13.eml]] with this
attachfile link:
https://github.com/jkitchin/scimax/blob/master/scimax-org.el#L727

It works for pdf export anyway.


Allen S. Rout writes:

> I've got a document structure I'd like to use, and I've been thinking
> about how to do it.   I thought I'd float the idea, and see if anyone
> has attempted something similar.
>
> I'm writing some prose, in which I'm referring to email messages.  In
> magical rainbow-pony land, my use case would look something like
>
> -----------
>
> Text text text blah blah relevant point, see [[ref: ./2004-01-13.eml]]
> blah blah more prose.
>
> ------------
>
> A footnote/endnote signifier would be placed in the prose at the point
> of the ref, and the contents of the file would be included in an
> appendix section.
>
> I've been searching on 'appendix', and the references seem mostly to
> talk about _formatting_ the section we deem an appendix, in the
> appropriate style.   I understand the value of this, but it's not my case.
>
> Should I just define a section, #+INCLUDE each email I care about, and
> do an internal link?  That's not awful, but it's not nearly as
> high-speed and sexy.
>
>
> - Allen S. Rout


-- 
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

      reply	other threads:[~2016-08-18 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 21:13 back matter in Org documents Allen S. Rout
2016-08-18 22:10 ` John Kitchin [this message]

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=m2h9ahiv8a.fsf@Johns-MacBook-Air.local \
    --to=jkitchin@andrew.cmu.edu \
    --cc=asr@ufl.edu \
    --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).