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: Thu, 19 Mar 2015 08:36:36 +0100	[thread overview]
Message-ID: <87vbhxzbej.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87egomtfpy.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 18 Mar 2015 17:47:37 +0100")

Rasmus <rasmus@gmx.us> writes:

> Keywords are akin to small headings to identify the contents of a
> document.  I see no reason to restrict this to the reader of the
> electronic version of a document.

What are you talking about? I don't want to restrict anything: AFAIU,
the feature you propose already exists in another form.

Again, your proposal is to have KEYWORDS mix two different things, i.e.,
set meta-data in document's header and set contents in the document. My
opinion is that for a given topic, you probably don't always want the
same contents, e.g., in "\\hyperref{pdfkeywords={...}}" and at the
beginning of the document, if only for the limitations on the syntax
allowed in the former.

Therefore, we may consider keeping the two features separated.

Do you think that you /always/ want "pdfkeywords" to hold exactly the
same contents as what you could put in your document? 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?


  reply	other threads:[~2015-03-19  7:35 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 [this message]
2015-03-19 10:19           ` Rasmus
2015-03-21  8:50             ` Nicolas Goaziou
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:

  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=87vbhxzbej.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \


* 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


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).