From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: [RFC] Replace some HTML related keywords with OPTIONS items
Date: Fri, 21 Jun 2013 14:16:03 -0600 [thread overview]
Message-ID: <87y5a3p6d8.fsf@gmail.com> (raw)
In-Reply-To: <87a9mjfg4h.fsf@gmail.com> (Nicolas Goaziou's message of "Fri, 21 Jun 2013 20:55:26 +0200")
>>> As for the move from #+OPTIONS: key:value to #+OPTIONS: :key value,
>>> I can provide a patch, but it will break export in many documents.
>>> A workaround would be to support both versions and document only the
>>> newest one.
>>
>> I didn't know supporting both styles was in the cards. If it isn't
>> overly complicated, that would be welcome of course.
>
> Here is a preliminary patch. It doesn't update org.texi yet.
>
> I find the new syntax weird for one character keys:
>
> #+OPTIONS: :* t :e t :: t :f t :- t :^ t :| t
>
I'm not sure how to weight aesthetics against consistency, but
personally I much prefer the previous
#+OPTIONS: *:t e:t ::t f:t -:t ^:t |:t
to the new possibility posted above. In my opinion it is not as
important to be consistent with code block header arguments here as it
is to be legible. All header arguments are full words and typically
have longer values, so they don't run into the same readability issues.
Just my 2¢
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-06-21 20:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 19:20 [RFC] Replace some HTML related keywords with OPTIONS items Nicolas Goaziou
2013-06-20 19:36 ` Nicolas Goaziou
2013-06-20 21:29 ` Samuel Wales
2013-06-21 4:51 ` Achim Gratz
2013-06-21 7:41 ` Sebastien Vauban
2013-06-21 9:17 ` Eric Abrahamsen
2013-06-21 9:26 ` Carsten Dominik
2013-06-21 17:28 ` Nicolas Goaziou
2013-06-21 17:32 ` Rick Frankel
2013-06-21 17:56 ` Achim Gratz
2013-06-21 18:55 ` Nicolas Goaziou
2013-06-21 19:36 ` Samuel Wales
2013-06-21 20:05 ` Thorsten Jolitz
2013-06-21 20:16 ` Eric Schulte [this message]
2013-06-21 20:41 ` Achim Gratz
2013-06-23 21:55 ` Carsten Dominik
2013-06-24 17:19 ` Achim Gratz
2013-06-27 14:26 ` Bastien
2013-06-27 14:33 ` Bastien
2013-06-27 16:00 ` Nicolas Goaziou
2013-06-27 16:19 ` Bastien
2013-06-27 19:18 ` Nicolas Goaziou
2013-06-28 7:14 ` Bastien
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=87y5a3p6d8.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=Stromeko@nexgo.de \
--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).