emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Latex summary
Date: Mon, 13 Feb 2017 13:59:13 -0600	[thread overview]
Message-ID: <CA+M2ft82vyXGbsOeW7NGtH8W96rX=h6nLNDZNQp0ye+viyBhSQ@mail.gmail.com> (raw)
In-Reply-To: <20170213194408.GS3623@volibear.adamsinfoserv.com>

On Mon, Feb 13, 2017 at 1:44 PM, Russell Adams
<RLAdams@adamsinfoserv.com> wrote:
> On Mon, Feb 13, 2017 at 03:14:31PM +0000, Eric S Fraga wrote:
>> On Monday, 13 Feb 2017 at 13:06, Russell Adams wrote:
>> > On Sun, Feb 12, 2017 at 04:30:48PM +0000, Eric S Fraga wrote:
>>
>> [...]
>>
>> >> Maybe use #index: ?
>> >
>> > Sorry, but do you mean in Latex or Org?
>>
>> Sorry.  Not clear in my response!  The #+index: is an org directly.
>>
>> "#+index: keyword" directives are then translated to LaTeX
>> \index{keyword} when exporting to PDF (say) and which can then be used
>> to create an index of keywords and page numbers using the \printindex
>> directive in LaTeX and the makeindex command to process these.  You'll
>> have to modify org-latex-pdf-process to invoke makeindex or else do this
>> manually from the exported LaTeX file.
>>
>> See attached for a minimal example (org and resulting PDF).
>>
>> --
>> : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.4-242-g2c27b8
>
> 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.
>
> Essentially what I'm doing is like this.
>
> * Issue A
>
> ** Details
>
> lorem ipsum.........
>
> /Recommendation: I would recommend that you do X/
>
> * Issue B
>
> ** Details
>
> lorem ipsum.........
>
> /Recommendation: Other customers are recommended to do Y/
>
> * Conclusion
>
> #babel to grep the file for recommendations#
>
>  - I would recommend that you do X
>  - Other customers are recommended to do Y
>

I'm dialing in super late, but seeing this format made me think of
using inline todos for this. Could that be possible? I haven't tried a
test case, but made me think:

- insert inline todos where you have your recommendations below
- maybe use special tag or todo keyword
- create agenda view via elisp src block that could spit out the
results in your conclusions section
- I'm sure someone here could get the ID/link inserted :)

Any interest in trying something like that?

Here was some discussion about inline todos and the comments package.
Looks like Eric was in on that discussion as well!
- https://lists.gnu.org/archive/html/emacs-orgmode/2011-04/msg00190.html


John

>
>
> So essentially I'm putting a summary at the end, like a list of
> conclusions. I'm not using single words. Linking back to the section
> where the recommendation came from would be ideal.
>
> I'm trying to figure out what this would be called, so I can check the
> Latex libraries. I expect it's fairly common, but that I'm using a
> poor choice of words to describe it.
>
>
>
> ------------------------------------------------------------------
> Russell Adams                            RLAdams@AdamsInfoServ.com
>
> PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/
>
> Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>

  reply	other threads:[~2017-02-13 19:59 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 [this message]
     [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='CA+M2ft82vyXGbsOeW7NGtH8W96rX=h6nLNDZNQp0ye+viyBhSQ@mail.gmail.com' \
    --to=jw.hendy@gmail.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).