all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Albert Krewinkel <albert+orgmode@zeitkraut.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Question on nested-blocks syntax
Date: Fri, 06 May 2016 14:01:43 +0200	[thread overview]
Message-ID: <874mabiee0.fsf@saiph.selenimh> (raw)
In-Reply-To: <8737pv8osk.fsf@espresso.zeitkraut.de> (Albert Krewinkel's message of "Fri, 06 May 2016 12:27:07 +0200")

Albert Krewinkel <albert+orgmode@zeitkraut.de> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

>> I don't think so. It would introduce unnecessary complexity.
>
> I guess that makes sense.  Too bad, though.

My answer was terse. Let me elaborate a bit.

There are a few issues that come to mind when considering this. 

First, you cannot use regexps to parse an example block anymore. You
have to read a line after another until you find the end of the block.
This is more complex.

Also, it defeats the "-i" flag, which allows an user to ignore
indentation in an example block.

In any case, as long as fontification is not based on top of the parser,
I think we should refrain from introducing too deep changes in the
syntax without a serious motivation (e.g., speed concerns, or ambiguous
cases) behind it. I sympathize with aesthetics concerns, Org syntax,
particularly blocks, is "massive", but I think this is not a sufficient
motivation here.

Regards,

  reply	other threads:[~2016-05-06 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06  9:20 Question on nested-blocks syntax Albert Krewinkel
2016-05-06 10:06 ` Nicolas Goaziou
2016-05-06 10:27   ` Albert Krewinkel
2016-05-06 12:01     ` Nicolas Goaziou [this message]
2016-05-07 18:09       ` Rasmus
2016-05-08 13:52         ` Nicolas Goaziou
2016-05-08 21:22           ` Rasmus

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=874mabiee0.fsf@saiph.selenimh \
    --to=mail@nicolasgoaziou.fr \
    --cc=albert+orgmode@zeitkraut.de \
    --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 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.