emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: simplify usage of special blocks (for beamer)
Date: Sun, 02 Dec 2018 21:42:54 +0100	[thread overview]
Message-ID: <87zhtnk6cx.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAELgYhe6=nM-PUg9mCXic=BJxW-O2Td1vOTtRbxukFAhSM5Bwg@mail.gmail.com> (Carlos Pita's message of "Sat, 1 Dec 2018 16:23:12 -0300")

Hello,

Carlos Pita <carlosjosepita@gmail.com> writes:

> One thing the core parser could do is to put the remaining of the
> opening line of a special block into an :args or similar property of
> the special block element, leaving it otherwise unparsed.

I thought about it a long time ago. However, I could not, and still
cannot, find an interesting use case for it in Org. This is a good
indicator that we do not need the feature.

> This is in the same spirit than what it already do for the affiliated
> attrs_X element.

Not really. 

For source blocks, arguments on the same line as the opening string
"BEGIN_SRC" are treated as a "HEADER" affiliated argument, which is
specific to Babel. OTOH, although almost every element type can have
affiliated keywords, only a small part could accept such "special
parameters". In a nutshell, this isn't symmetrical.

> It's not a lot of help but it would at least spare
> backends from having to parse the remaining of the opening line as
> I did.

So far, none of our back-ends need this, even though they are relatively
complex.

So, we could use the room there if one day, we need it for something,
but until then, I don't think we should extend syntax just because we
can do it.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2018-12-02 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 16:24 Feature request: simplify usage of special blocks (for beamer) Carlos Pita
2018-12-01 18:28 ` Eric S Fraga
2018-12-01 18:41   ` Carlos Pita
2018-12-01 19:23     ` Carlos Pita
2018-12-02 11:58       ` Eric S Fraga
2018-12-02 14:50         ` Carlos Pita
2018-12-02 15:30           ` Carlos Pita
2018-12-02 20:42       ` Nicolas Goaziou [this message]
2018-12-02 21:05         ` Carlos Pita
2018-12-02 11:55     ` 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=87zhtnk6cx.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=carlosjosepita@gmail.com \
    --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

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).