emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ox, patch] Keywords & what should go in ox?
Date: Sat, 21 Mar 2015 09:50:57 +0100	[thread overview]
Message-ID: <87fv8y4tu6.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <877fudb87p.fsf@gmx.us> (rasmus@gmx.us's message of "Thu, 19 Mar 2015 11:19:22 +0100")

Rasmus <rasmus@gmx.us> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Do you think that you /always/ want "pdfkeywords" to hold exactly the
>> same contents as what you could put in your document?
>
> You as in me: yes most certainly.

IIUC, it contradicts your initial post where you wanted, at some later
time, to add bells and whistles to keywords displayed in the output
(e.g., turning them into links).

I'm not very keen on the idea of KEYWORD doing two different things. If
that's not the case, I'm fine with it.

>> Do you think that a user who wants to fill pdfkeywords will always want
>> to also add these contents in the body of the document?
>
> Which is why the patch provided a switch in #+OPTIONS.

The switch is all or nothing. Again, you're talking about two different
features : keywords in meta-data and keywords in data.


Regards,

  reply	other threads:[~2015-03-21  8:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 13:55 Rasmus
2015-03-15  8:28 ` Nicolas Goaziou
2015-03-17 15:37   ` Rasmus
2015-03-17 15:46     ` Nicolas Goaziou
2015-03-18 16:47       ` Rasmus
2015-03-19  7:36         ` Nicolas Goaziou
2015-03-19 10:19           ` Rasmus
2015-03-21  8:50             ` Nicolas Goaziou [this message]
2015-03-26 19:31   ` Rasmus
2015-03-26 20:37     ` Nicolas Goaziou
2015-03-27 12:50       ` Rasmus
2015-03-28 15:21         ` Nicolas Goaziou
2015-03-28 15:50           ` Rasmus
2015-03-29 12:16           ` 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=87fv8y4tu6.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).