From: Joe Hirn <joseph.hirn@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-export-latex-hyperref-options-format
Date: Wed, 19 Feb 2014 16:43:20 -0600 [thread overview]
Message-ID: <CALY_e1rogor3qbcB_giGJTWHWw0T6QOZg2+euMTL_-TVfaYAXQ@mail.gmail.com> (raw)
In-Reply-To: <878ut72qyo.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
Hi just sat down to code this up. I assume the keywords are so we can use
data within the plist argument (info) passed to `org-latex-template'. But
I'm not exactly sure what you mean by %k for keywords.
Are you suggesting we could do something like:
"\\hypersetup{\n pdfkeywords={%kkeywords},\n
pdfsubject={%kdescription},\n pdfcreator={%kcreator}}\n"
If that's the idea, is there a more powerful construct than regex matching
for achieving this? Otherwise, can you give me an example of what you had
in mind for the keyword placeholders.
Thanks
On Wed, Feb 19, 2014 at 7:05 AM, Nicolas Goaziou <n.goaziou@gmail.com>wrote:
> Hello,
>
> Joe Hirn <joseph.hirn@gmail.com> writes:
>
> > So I understand, you're recommending I disable org-latex-with-hyperref
> and
> > then add my own \\hypersetup. My goal would be to avoid placing a #+
> entry
> > into every .org file I compose. Which var would be the easiest to to
> adjust
> > so I can emit \\hypersetup by default and still access the info map that
> is
> > passed to org-latex-template. I'd like to get the keywords, subject and
> > creator variables that are emitted right now.
>
> On a personal level, if you only need to add keyword-value pairs,
> I think the simplest solution is to add a class in `org-latex-classes',
> where you insert an additional "\hypersetup{...}" command. You don't
> need to change `org-latex-with-hyperref' in this case.
>
> You can also use a (final) filter to install this command if you don't
> want to bother creating a new class.
>
> On a more general level, I'll welcome a solution replacing
> `org-latex-with-hyperref' with `org-latex-hyperref-template', which
> could be either nil (no hyperref command) or a string with some
> placeholders (e.g. %k for keywords).
>
> What do you think?
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 2562 bytes --]
next prev parent reply other threads:[~2014-02-19 22:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 20:41 org-export-latex-hyperref-options-format Joe Hirn
2014-02-17 22:13 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-02-17 22:59 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-17 23:23 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-02-17 23:42 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-19 13:05 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-02-19 16:21 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-19 22:43 ` Joe Hirn [this message]
2014-02-20 10:22 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-02-20 12:34 ` org-export-latex-hyperref-options-format Joseph Hirn
2014-02-20 17:58 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-20 20:51 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-02-20 21:52 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-20 22:53 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-21 17:28 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-02-21 18:35 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-22 9:39 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-02-22 16:42 ` org-export-latex-hyperref-options-format Joe Hirn
2014-02-22 17:02 ` org-export-latex-hyperref-options-format Bastien
2014-02-24 21:51 ` org-export-latex-hyperref-options-format Joe Hirn
2014-03-21 8:00 ` org-export-latex-hyperref-options-format Bastien
2014-03-21 13:03 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-03-21 13:06 ` org-export-latex-hyperref-options-format Bastien
2014-03-21 16:51 ` org-export-latex-hyperref-options-format Thomas S. Dye
2014-03-21 17:11 ` org-export-latex-hyperref-options-format Joe Hirn
2014-03-21 17:23 ` org-export-latex-hyperref-options-format Nicolas Goaziou
2014-03-21 18:38 ` org-export-latex-hyperref-options-format Thomas S. Dye
2014-03-21 21:19 ` org-export-latex-hyperref-options-format Nick Dokos
2014-03-21 21:47 ` org-export-latex-hyperref-options-format Thomas S. Dye
2014-03-21 22:19 ` org-export-latex-hyperref-options-format Charles Millar
2014-03-21 22:39 ` org-export-latex-hyperref-options-format Nick Dokos
2014-03-22 18:26 ` org-export-latex-hyperref-options-format Thomas S. Dye
2014-03-23 21:39 ` org-export-latex-hyperref-options-format Thomas S. Dye
2014-02-17 23:25 ` org-export-latex-hyperref-options-format Rasmus
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=CALY_e1rogor3qbcB_giGJTWHWw0T6QOZg2+euMTL_-TVfaYAXQ@mail.gmail.com \
--to=joseph.hirn@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).