From: Eduardo Mercovich <eduardo@mercovich.net>
To: Russell Adams <RLAdams@AdamsInfoServ.Com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Latex summary
Date: Mon, 13 Feb 2017 08:08:37 -0300 [thread overview]
Message-ID: <87k28ue4ay.fsf@biologica.mercovich.net> (raw)
In-Reply-To: <20170212001601.GK3623@volibear.adamsinfoserv.com>
Hi Russell.
> 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?
A reversed ToC seems perfect, since it will give you also a link to the
original place where it is developed.
I do use LaTex from Org so I'm not any expert, but I believe that this "Add
an item in the table of contents" in StackExchange may be useful.
http://tex.stackexchange.com/questions/119719/add-an-item-in-the-table-of-contents
Best...
--
eduardo mercovich
Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
(Anónimo)
next prev parent reply other threads:[~2017-02-13 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 0:16 Latex summary Russell Adams
2017-02-13 11:08 ` Eduardo Mercovich [this message]
[not found] <ffdbc677680d4f86a436ce5c969b0289@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-12 16:30 ` Eric S Fraga
2017-02-13 13:06 ` 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
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=87k28ue4ay.fsf@biologica.mercovich.net \
--to=eduardo@mercovich.net \
--cc=RLAdams@AdamsInfoServ.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).