From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: Latex summary
Date: Mon, 13 Feb 2017 19:55:10 +0000 [thread overview]
Message-ID: <87wpctq31d.fsf@ucl.ac.uk> (raw)
In-Reply-To: 9de9f242d97c4a819fbcd2b168d9d8ae@HE1PR01MB1898.eurprd01.prod.exchangelabs.com
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
On Monday, 13 Feb 2017 at 19:44, Russell Adams wrote:
[...]
> Eric, thanks for that really detailed input. I'll have to consider
> it. I worry that the keywords aren't like the full sentences I'm
> using.
Ah, okay.
Well, I'm not sure there is anything in LaTeX that does this as such but
you could play around with inline tasks. You could use an inline task
to give the recommendation and then use
org-latex-format-inlinetask-function
to specify your own function that would, for instance, output the
recommendation inline but also create an endnote (cf. endnotes LaTeX
package) for the summary at the end?
I do this for collecting TODO items when I'm writing a proposal or
paper. My function looks like this:
#+begin_src emacs-lisp
;; define what to do with inline tasks: use endnote
(defun esf/org-format-inlinetask-as-endnote (todo type priority name tags contents info)
"Format an inline task element for LaTeX export."
(let ((theinlinetask (concat " " name ": " contents)))
(if (and todo (not (equal todo "NOTE")))
(format "\\endnote{%s}\\marginpar{\\fbox{\\tiny E\\theendnote. %s}}" theinlinetask todo)
(format "\\hl{%s}" contents))))
(setq-local org-latex-format-inlinetask-function
'esf/org-format-inlinetask-as-endnote)
#+end_src
Although I don't put any text inline, you could easily do so.
HTH,
eric
--
: 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 --]
next prev parent reply other threads:[~2017-02-13 21:29 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 ` Latex summary 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 [this message]
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=87wpctq31d.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).