From: "Nicolas Richard" <theonewiththeevillook@yahoo.fr>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Org syntax (draft)
Date: Wed, 13 Mar 2013 15:07:54 +0100 [thread overview]
Message-ID: <877glb2y11.fsf@yahoo.fr> (raw)
In-Reply-To: 87y5dxzgvo.fsf@gmail.com
Hi,
I obviously did not send and actually lost a message I prepared two days
ago. I'll try again.
>> I suggest adding : The number of stars defines the level of the
>> headline.
>
> Does it belong to the syntax definition? Level is how Org uses syntax
> internally. Also the sentence, although right, is misleading, because
> level definition also depends on `org-odd-levels-only'.
I think it's partly in the syntax, since it defines "parentness" for
headlines (the numeric level is of no importance, but the relative level
is used).
>
>> I suggest dropping "Case is significant" (or maybe give the whole story :
>> IIRC, it is the ascii code of the given letter that is used as
>> priority)
>
> I'm not sure that the purpose of this document should be to explain how
> syntax will be used.
That is why I suggested dropping the mention : case is not significant
for the syntax. Very minor though, obviously.
>> That should be `org-comment-string' I guess.
>
> Indeed. Btw, I think this variable should be a defconst, not
> a defcustom. It just makes things harder for little benefit.
As you know, "Comment" is also a french word meaning "how", and that
could very well appear uppercased as the first word of a title. (I'd
personally recommend against uppercasing titles, but I'd understand if
someone wanted to customize the word for such reasons)
> Would you (or Someone) mind updating the org-syntax.org file on Worg?
Please review the attached patch and apply parts as you wish (even if I
wanted to do it myself, I don't have worg access.)
Last word about #+TBLFM: I'm not sure if that should go into the "affiliated
keywords" section (thus rewriting parts of it, because that one goes
below the table, unlike other affiliated keywords) or a special section
on its own. Thus I'm not changing anything wrt that.
From f97c00bfbd8a14d0b2953ee0e8b6817a2b9f0306 Mon Sep 17 00:00:00 2001
From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Date: Mon, 11 Mar 2013 16:25:21 +0100
Subject: [PATCH] dev/org-syntax.org: minor
---
dev/org-syntax.org | 34 +++++++++++++++++++---------------
1 file changed, 19 insertions(+), 15 deletions(-)
diff --git a/dev/org-syntax.org b/dev/org-syntax.org
index 9b2a843..a918a75 100644
--- a/dev/org-syntax.org
+++ b/dev/org-syntax.org
@@ -15,7 +15,8 @@ within specific environments.
Three categories are used to classify these environments: "Greater
elements", "elements", and "objects", from the broadest scope to the
-narrowest.
+narrowest. The word "element" is used for both Greater and non-Greater
+elements, the context should make that clear.
The paragraph is the unit of measurement. An element defines
syntactical parts that are at the same level as a paragraph,
@@ -41,16 +42,17 @@ Unless specified otherwise, case is not significant.
STARS KEYWORD PRIORITY TITLE TAGS
#+END_EXAMPLE
- STARS is a string starting at column 0 and containing at least one
+ STARS is a string starting at column 0, containing at least one
asterisk (and up to ~org-inlinetask-min-level~ if =org-inlinetask=
- library is loaded). It's the sole compulsory part of a headline.
+ library is loaded) and ended by a space character. The number of
+ asterisks is used to define the level of the headline. It's the
+ sole compulsory part of a headline.
KEYWORD is a TODO keyword, which has to belong to the list defined
- in ~org-todo-keywords~. Case is significant.
+ in ~org-todo-keywords-1~. Case is significant.
PRIORITY is a priority cookie, i.e. a single letter preceded by
- a hash sign # and enclosed within square brackets. Case is
- significant.
+ a hash sign # and enclosed within square brackets.
TITLE can be made of any character but a new line. Though, it will
match after every other part have been matched.
@@ -71,7 +73,7 @@ Unless specified otherwise, case is not significant.
,**** TODO [#A] COMMENT Title :tag:a2%:
#+END_EXAMPLE
- If the first word appearing in the title is ~org-comment-keyword~,
+ If the first word appearing in the title is ~org-comment-string~,
the headline will be considered as "commented". If that first word
is ~org-quote-string~, it will be considered as "quoted". In both
situations, case is significant.
@@ -82,14 +84,14 @@ Unless specified otherwise, case is not significant.
If ~org-archive-tag~ is one of its tags, it will be considered as
"archived". Case is significant.
- A headline contains directly at most one section, followed by any
- number of headlines. Only a section can contain another section.
+ A headline contains directly one section, followed by any
+ number of deeper level headlines.
A section contains directly any greater element or element. Only
a headline can contain a section. As an exception, text before the
first headline in the document also belongs to a section.
- In a quoted headline contains a section, the latter will be
+ If a quoted headline contains a section, the latter will be
considered as a "quote section".
As an example, consider the following document:
@@ -136,7 +138,8 @@ Unless specified otherwise, case is not significant.
attributes.
This is done by adding specific keywords, named "affiliated
- keywords", just above the element considered, no blank line allowed.
+ keywords", just above the element considered, no blank line
+ allowed.
Affiliated keywords are built upon one of the following patterns:
"#+KEY: VALUE", "#+KEY[OPTIONAL]: VALUE" or "#+ATTR_BACKEND: VALUE".
@@ -150,7 +153,7 @@ Unless specified otherwise, case is not significant.
OPTIONAL and VALUE can contain any character but a new line. Only
"CAPTION" and "RESULTS" keywords can have an optional value.
- An affiliated keyword can appear on multiple lines if KEY is either
+ An affiliated keyword can appear more than once if KEY is either
"CAPTION" or "HEADER" or if its pattern is "#+ATTR_BACKEND: VALUE".
"CAPTION", "AUTHOR", "DATE" and "TITLE" keywords can contain objects
@@ -183,7 +186,8 @@ Unless specified otherwise, case is not significant.
NAME can contain any non-whitespace character.
- PARAMETERS can contain any character, and can be omitted.
+ PARAMETERS can contain any character other than new line, and can
+ be omitted.
If NAME is "CENTER", it will be a "center block". If it is
"QUOTE", it will be a "quote block".
@@ -191,8 +195,8 @@ Unless specified otherwise, case is not significant.
If the block is neither a center block, a quote block or a [[#Blocks][block
element]], it will be a "special block".
- CONTENTS can contain any element, but another greater block of the
- same type.
+ CONTENTS can contain any element, except : a line =#+END_NAME= on
+ its own and lines beginning with STARS must be quoted by a comma.
** Drawers and Property Drawers
:PROPERTIES:
--
1.8.1.4
next prev parent reply other threads:[~2013-03-13 14:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 20:37 [RFC] Org syntax (draft) Nicolas Goaziou
2013-03-07 20:47 ` Carsten Dominik
2013-03-07 22:07 ` Achim Gratz
2013-03-08 10:04 ` Bastien
2013-03-08 10:39 ` was: " Andreas Röhler
2013-03-08 10:46 ` (no subject) Bastien
2013-03-08 10:59 ` Andreas Röhler
2013-03-08 11:05 ` Bastien
2013-03-08 11:18 ` Andreas Röhler
2013-03-08 11:23 ` Bastien
2013-03-08 13:00 ` Andreas Röhler
2013-03-08 13:12 ` Bastien
2013-03-08 15:22 ` Andreas Röhler
2013-03-08 15:40 ` Bastien
2013-03-08 20:39 ` T.F. Torrey
2013-03-08 21:19 ` Nicolas Goaziou
2013-03-08 21:57 ` Suvayu Ali
2013-03-08 22:15 ` interoperability matters " Gregor Zattler
2013-03-09 14:09 ` Bastien
2013-03-10 22:40 ` T.F. Torrey
2013-03-08 13:25 ` [RFC] Org syntax (draft) François Pinard
2013-03-08 15:23 ` Nicolas Richard
2013-03-08 22:06 ` Nicolas Goaziou
2013-03-09 10:52 ` Waldemar Quevedo
2013-03-09 14:23 ` Carsten Dominik
2013-03-09 14:42 ` Nicolas Goaziou
2013-03-09 15:05 ` Carsten Dominik
2013-03-15 20:22 ` Nicolas Goaziou
2013-03-17 18:48 ` Samuel Wales
2013-04-05 17:01 ` Bastien
2013-03-13 14:07 ` Nicolas Richard [this message]
2013-03-15 20:39 ` Nicolas Goaziou
2013-03-09 23:16 ` Achim Gratz
2013-03-09 23:49 ` Nicolas Goaziou
2013-03-10 4:35 ` Jambunathan K
2013-03-10 7:08 ` Nicolas Goaziou
2013-03-10 10:14 ` Bastien
2013-03-10 10:16 ` Bastien
2013-03-10 13:07 ` Achim Gratz
2013-03-10 14:11 ` Bastien
2013-03-10 16:02 ` Achim Gratz
2013-03-10 16:09 ` Jambunathan K
2013-03-10 17:12 ` Achim Gratz
2013-03-10 21:44 ` Jonathan Leech-Pepin
2013-03-10 15:44 ` Jambunathan K
2013-03-14 16:58 ` Eric S Fraga
2013-03-14 18:26 ` Jambunathan K
2013-03-14 18:51 ` David Engster
2013-03-14 19:03 ` [Out-of-Thread] " Jambunathan K
2013-03-14 19:15 ` David Engster
2013-03-14 19:23 ` Jambunathan K
2013-03-14 19:29 ` David Engster
2013-03-14 19:52 ` Jambunathan K
2013-04-09 16:37 ` Bastien
2013-03-17 7:18 ` Achim Gratz
2013-03-17 9:36 ` Sebastien Vauban
-- strict thread matches above, loose matches on Subject: below --
2013-03-12 10:19 orgmode
2013-03-13 15:33 ` Nicolas Goaziou
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=877glb2y11.fsf@yahoo.fr \
--to=theonewiththeevillook@yahoo.fr \
--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).