emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: Latex summary
Date: Sun, 12 Feb 2017 16:30:48 +0000	[thread overview]
Message-ID: <877f4vwevb.fsf@ucl.ac.uk> (raw)
In-Reply-To: <ffdbc677680d4f86a436ce5c969b0289@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Russell Adams's message of "Sun, 12 Feb 2017 00:16:01 +0000")

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

On Sunday, 12 Feb 2017 at 00:16, Russell Adams wrote:
> I frequently write documentation with recommendations nested in
> different sections, typically one line per recommendation. I then
> summarize a list of those recommendations at the end of my document.
>
> Today I use babel to grep the document for my recommendation format,
> but given I'm exporting to Latex can anyone suggest a better method?
> Something like a reversed table of contents?

Maybe use #index: ?

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

       reply	other threads:[~2017-02-12 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ffdbc677680d4f86a436ce5c969b0289@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-12 16:30 ` Eric S Fraga [this message]
2017-02-13 13:06   ` Latex summary Russell Adams
     [not found]   ` <7ed2978596ff4adb8aceaae2fa7393bc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-13 15:14     ` Eric S Fraga
2017-02-13 19:44       ` Russell Adams
2017-02-13 19:59         ` John Hendy
     [not found]       ` <9de9f242d97c4a819fbcd2b168d9d8ae@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-13 19:55         ` Eric S Fraga
2017-02-13 15:14     ` Eric S Fraga
2017-02-12  0:16 Russell Adams
2017-02-13 11:08 ` Eduardo Mercovich

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=877f4vwevb.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).