From: "Gustav Wikström" <gustav@whil.se>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Proposal for new document-level syntax
Date: Sat, 1 Jun 2019 15:53:17 +0000 [thread overview]
Message-ID: <HE1PR02MB30336D085EE8406A1A94B737DA1A0@HE1PR02MB3033.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <8736ktfnre.fsf@ucl.ac.uk>
Hi Eric!
> -----Original Message-----
> From: Fraga, Eric <e.fraga@ucl.ac.uk>
> Sent: den 1 juni 2019 15:18
> To: Gustav Wikström <gustav@whil.se>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [O] Proposal for new document-level syntax
>
> For me, however, your proposed structure would clash strongly with my
> usual working practice. Specifically, I put all customizations and
> settings at the end of my documents, along with, for instance, Emacs
> file local variables. These are things I do not change often and
> usually don't care to see. At the start of the document, however, is
> the real content. So, I don't particularly like the idea of having
> settings etc. *before* the content in my files.
Point taken. File local variables potitions would not be affected of
course. And to be honest, I don't see any existing keyword going away
any time soon either. So your workflow probably won't be affected for
a long time. Unless you choose to!
With that said, I'd still like to argue a bit more for the structure
I've presented. The idea with having drawers is exactly the point
you're also making; that it makes configuration go out of the way for
real content. I question the disctraction 1-2 rows provide. Take for
example the way current property drawer and planning-properties work
on outline-nodes. They have fixed positions at the top of the node and
take up maximum two rows when declared. Not really an issue in my book
and the benefit of fixed positions is easy parsing for both humans and
the machine. The same would apply for document settings and
properties. Take the example below:
#+begin_example
:SETTINGS:...
:PROPERTIES:...
,* Heading 1
DEADLINE: <2019-06-02 Sun> SCHEDULED: <2019-06-01 Sat>
:PROPERTIES:...
lorem
,* Heading 2
Ipsum
,# -*- mode: org -*-
#+end_example
To me it makes perfect sense to have the drawers at the top at fixed
positions. It follows current convention for headlines. At most two
rows before the real content is hopefully a compromize that can be
made for syntactic clarity and simplicity. And personally it would be
a great improvement over the current way document-level keywords work.
>
> Just by 2¢.
Thanks!
next prev parent reply other threads:[~2019-06-01 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 10:15 Proposal for new document-level syntax Gustav Wikström
2019-06-01 13:17 ` Fraga, Eric
2019-06-01 13:45 ` Achim Gratz
2019-06-01 14:01 ` Fraga, Eric
2019-06-01 15:53 ` Gustav Wikström [this message]
2019-06-01 21:00 ` Nicolas Goaziou
2019-06-01 23:08 ` Gustav Wikström
2019-06-03 20:39 ` Nicolas Goaziou
2019-06-06 7:50 ` Gustav Wikström
2019-06-02 7:35 ` Norman Walsh
2019-06-02 22:49 ` Samuel Wales
2019-06-06 9:29 ` Marco Wahl
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=HE1PR02MB30336D085EE8406A1A94B737DA1A0@HE1PR02MB3033.eurprd02.prod.outlook.com \
--to=gustav@whil.se \
--cc=e.fraga@ucl.ac.uk \
--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).