From: Matt Lundin <mdl@imapmail.org>
To: emacs-orgmode@gnu.org
Subject: Re: Allowing loose ordering in Org files
Date: Tue, 10 Nov 2015 14:42:14 -0600 [thread overview]
Message-ID: <87si4dlh7d.fsf@fastmail.fm> (raw)
In-Reply-To: <m2fv0d39oe.fsf@Vulcan.attlocal.net> (John Wiegley's message of "Tue, 10 Nov 2015 12:02:09 -0800")
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> I really don't like the idea of making Org /syntax/ customizable, would it
>> be with the help of a hook or a variable.
>
> From what I've seen so far, several users want regularity of syntax to
> decide formatting, and several users want user preference to decide
> formatting. There do seem to be larger costs for letting the user
> decide; but there are also costs to not letting the user decide, that
> I feel are not being appreciated.
Could you please be more specific about what the problem is? Apart from
the location of properties, are there other forms of flexible formatting
that have been lost in recent releases? And what specifically is the
problem with a required property drawer location? Is it aesthetic?
Functional?
> The reason I'm sticking on this point is because it also relates to our future
> road map. If Org continues to do this -- to trade flexibility of formatting
> for regularity of parsing -- it might continue to alienate some of us.
I don't think this is a fair description of the direction org-mode has
been taking. I think org-mode has has unparalleled flexibility. If
anything, that flexibility has grown over the past few years. E.g., I
can enter any number of drawers, tables, lists, code blocks, links,
footnotes, etc. in a single entry. And I can export all of that data
reliable to a growing number of formats.
But when it comes to meta-data, I think it has been helpful to tighten
up the syntax. After all, org-mode has always required many types of
fixed formatting/syntax. For instance, one can't just put tags anywhere
in the body of an entry. Nor can one use arbitrary symbols to designate
headline levels. Nor can on put TODO keywords anywhere (despite frequent
requests for such functionality).
Since org-mode recognizes only one property drawer per entry, it makes
sense (for clarity, simplicity, efficiency, etc.) to require that this
special key:value metadata be "attached" to the headline (like tags,
TODOs, etc.).
Matt
next prev parent reply other threads:[~2015-11-10 20:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 0:11 bug in org-habits Mark A. Hershberger
2015-11-03 9:56 ` Marco Wahl
2015-11-03 11:16 ` Puneeth Chaganti
2015-11-03 13:11 ` John Wiegley
2015-11-03 13:46 ` Marco Wahl
2015-11-03 14:20 ` Stelian Iancu
2015-11-03 16:31 ` Nicolas Goaziou
2015-11-03 19:20 ` John Wiegley
2015-11-03 19:35 ` Nicolas Goaziou
2015-11-03 20:17 ` John Wiegley
2015-11-03 20:52 ` Nicolas Goaziou
2015-11-03 20:55 ` John Wiegley
2015-11-03 21:31 ` Achim Gratz
2015-11-03 21:36 ` John Wiegley
2015-11-03 21:48 ` Jonathan Leech-Pepin
2015-11-03 21:56 ` John Wiegley
2015-11-03 22:36 ` Achim Gratz
2015-11-03 22:45 ` John Wiegley
2015-11-04 13:01 ` Bastien Guerry
2015-11-04 20:26 ` John Wiegley
2015-11-09 15:13 ` Allowing loose ordering in Org files (Was: bug in org-habits) John Wiegley
2015-11-09 17:47 ` Allowing loose ordering in Org files Rasmus
2015-11-09 18:15 ` John Wiegley
2015-11-09 19:28 ` Rasmus
2015-11-09 19:57 ` John Wiegley
2015-11-09 19:12 ` Achim Gratz
2015-11-09 19:24 ` John Wiegley
2015-11-09 20:04 ` Achim Gratz
2015-11-09 21:13 ` Stelian Iancu
2015-11-09 21:30 ` John Wiegley
2015-11-10 1:40 ` Allowing loose ordering in Org files (Was: bug in org-habits) Aaron Ecay
2015-11-10 1:52 ` Allowing loose ordering in Org files John Wiegley
2015-11-10 5:31 ` Thomas S. Dye
2015-11-10 17:37 ` Nicolas Goaziou
2015-11-10 19:20 ` Thomas S. Dye
2015-11-10 20:02 ` John Wiegley
2015-11-10 20:42 ` Matt Lundin [this message]
2015-11-10 20:44 ` Matt Lundin
2015-11-10 17:51 ` Matt Lundin
2015-11-10 18:19 ` Matt Lundin
2015-11-10 19:49 ` Achim Gratz
2015-11-10 20:11 ` John Wiegley
2015-11-10 20:38 ` Achim Gratz
2015-11-10 22:35 ` John Wiegley
2015-11-11 16:13 ` Karl Voit
2015-11-10 11:30 ` Allowing loose ordering in Org files (Was: bug in org-habits) Stelian Iancu
2015-11-03 23:43 ` bug in org-habits Nicolas Goaziou
2015-11-04 1:01 ` John Wiegley
2015-11-04 9:02 ` Stelian Iancu
2015-11-04 9:16 ` Eric S Fraga
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=87si4dlh7d.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--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).