emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox, patch] Keywords & what should go in ox?
Date: Wed, 18 Mar 2015 17:47:37 +0100	[thread overview]
Message-ID: <87egomtfpy.fsf@gmx.us> (raw)
In-Reply-To: <87h9tj39uk.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 17 Mar 2015 16:46:43 +0100")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Rasmus <rasmus@gmx.us> writes:
>
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>
>>> We don't need a convoluted markup for that, let's keep it simple.
>>
>> But then you'd have to repeat data.  E.g.
>>
>> #+KEYWORDS: my keywords for meta-data that should also be printed.
>> my keywords for meta-data that should also be printed.
>>
>> This seems error prone and undesirable IMO.
>
> Except that this is not a real repetition. As you mentioned, in the
> latter case, you want to throw in links and probably other markup, which
> make no sense in plain meta-data.

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.

> IMO, this is over-engineering.

I disagree, but extrapolating this will go nowhere.

—Rasmus

-- 
Got mashed potatoes. Ain't got no T-Bone. No T-Bone

  reply	other threads:[~2015-03-18 16:47 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 [this message]
2015-03-19  7:36         ` Nicolas Goaziou
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:
  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=87egomtfpy.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).