From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Bastien <bzg@altern.org>, Org Mode List <emacs-orgmode@gnu.org>,
mail@christianmoe.com
Subject: Re: About commit named "Allow multi-line properties to be specified in property blocks"
Date: Thu, 03 Nov 2011 14:18:01 -0600 [thread overview]
Message-ID: <87mxcdeyy5.fsf@gmail.com> (raw)
In-Reply-To: 87aa8dgekw.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>>>> On the contrary, creating a block for each keyword would mean a lot of
>>>> new syntax.
>>>>
>>>> We currently have 8 types of blocks (not counting dynamic blocks, whose
>>>> syntax is a bit different), all requiring to be parsed differently:
>>>>
>>>> 1. Center blocks,
>>>> 2. Comment blocks,
>>>> 3. Example blocks,
>>>> 4. Export blocks,
>>>> 5. Quote blocks,
>>>> 6. Special blocks,
>>>> 7. Src blocks,
>>>> 8. Verse blocks.
>>>
>>> I'm not sure what do you mean by "requiring to be parsed differently".
>>> Can you explain it? I understand they should be treated differently by
>>> the exporters, but I don't understand why they would need to be parsed
>>> differently.
>>>
>>
>> I also wouldn't think of this as new syntax, I don't see 8 rules for the
>> 8 types above but rather one rule along the lines of #+begin_SOMETHING
>> where the SOMETHING can be anything.
>
> Well, certainly, from a "Press TAB on #+begin_ line", they have exactly
> the same meaning, and could as well be labelled #+begin_SOMETHING. But,
>
> - If I consider fontification, "Src blocks" differ from "Example
> blocks", which differ from everything else.
>
> - If I consider `org-edit-special', C-c ' will bring you to a buffer
> with a special mode in "Src blocks", fundamental mode in "Example
> blocks" and "Verse blocks".
>
> - If I consider lists, you can have them in "Quote blocks", but not in
> "Export blocks" or "Verse blocks", for example.
>
> - If I consider indentation, it will be ignored for "Example blocks"
> (and should do the same for "Verse blocks"), could do something
> entirely different on "Src blocks", and will indent normally,
> i.e. "Quote blocks".
>
> - If I consider recursion, you can have "Quote blocks" inside "Center
> blocks", but not inside "Export blocks".
>
> - If I consider options on the "begin_" line, "Example blocks" accept
> them, but not "Center blocks".
>
> - If I consider entities, you can have them in "Verse blocks" but not
> in "Example blocks"
>
> - If I consider export, obviously, they will all be treated very
> differently.
>
> And I'm pretty sure I'm forgetting some other case. So, yes, from the
> moon, they're pretty much indistinguishable ;) From an Org point of
> view, they have 8 different meanings and, as such, need to be parsed
> differently. At least, I've had to proceed that way when I wrote an Org
> parser.
>
Point made :), I concede a huge difference between block types.
I'm ultimately happy that the begin_property approach has not moved
forward.
Best -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-11-03 20:33 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 19:06 About commit named "Allow multi-line properties to be specified in property blocks" Nicolas Goaziou
2011-10-31 20:05 ` Eric Schulte
2011-10-31 20:49 ` Nicolas Goaziou
2011-10-31 21:30 ` Eric Schulte
2011-11-01 8:24 ` Nicolas Goaziou
2011-11-01 8:36 ` Nicolas Goaziou
2011-11-01 14:36 ` Eric Schulte
2011-11-01 15:39 ` Nicolas Goaziou
2011-11-01 16:58 ` Eric Schulte
2011-11-01 17:48 ` Christian Moe
2011-11-01 19:02 ` Eric Schulte
2011-11-01 19:45 ` Christian Moe
2011-11-01 20:22 ` Eric Schulte
2011-10-31 21:33 ` Christian Moe
2011-10-31 21:22 ` Christian Moe
2011-10-31 21:36 ` Eric Schulte
2011-11-01 7:33 ` Christian Moe
2011-11-02 15:35 ` Bastien
2011-11-02 17:39 ` Nicolas Goaziou
2011-11-03 1:26 ` Bastien
2011-11-03 8:08 ` Christian Moe
2011-11-03 15:10 ` Nick Dokos
2011-11-03 18:32 ` Eric Schulte
2011-11-03 20:01 ` Nicolas Goaziou
2011-11-03 20:18 ` Eric Schulte [this message]
2011-11-03 20:23 ` Eric Schulte
2011-11-04 8:02 ` Rainer M Krug
2011-11-04 17:48 ` Darlan Cavalcante Moreira
2011-11-04 19:25 ` Eric Schulte
2011-11-07 22:09 ` Eric Schulte
2011-11-08 8:42 ` Rainer M Krug
2011-11-08 9:31 ` Sebastien Vauban
2011-11-08 9:41 ` Rainer M Krug
2011-11-08 9:58 ` Sebastien Vauban
2011-11-08 10:06 ` Rainer M Krug
2011-11-08 14:42 ` Darlan Cavalcante Moreira
2011-11-08 15:06 ` Sebastien Vauban
2011-11-08 16:03 ` Eric Schulte
2011-11-08 22:53 ` Eric Schulte
2011-11-09 8:25 ` Rainer M Krug
2011-11-09 16:12 ` Eric Schulte
2011-11-09 17:18 ` Rainer M Krug
2011-11-09 22:31 ` Sebastien Vauban
2011-11-15 12:33 ` Rainer M Krug
2011-11-15 16:00 ` Eric Schulte
2011-11-15 16:37 ` Torsten Wagner
2011-11-15 16:56 ` Eric Schulte
2011-11-15 17:13 ` Thomas S. Dye
2011-11-15 18:22 ` Eric Schulte
2011-11-15 17:24 ` Rainer M Krug
2011-11-08 9:41 ` Sebastien Vauban
2011-11-08 9:44 ` Rainer M Krug
2011-11-08 16:01 ` Eric Schulte
2011-11-02 21:05 ` Samuel Wales
2011-11-02 21:21 ` Samuel Wales
2011-11-03 1:42 ` Bastien
2011-11-03 8:19 ` Christian Moe
2011-11-03 18:34 ` Eric Schulte
2011-11-03 18:59 ` Eric Schulte
2011-11-09 17:40 ` Samuel Wales
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mxcdeyy5.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.