From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlos Pita Subject: Re: Feature request: simplify usage of special blocks (for beamer) Date: Sat, 1 Dec 2018 16:23:12 -0300 Message-ID: References: <87a7lpxfsc.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55156) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gTArP-0005oz-8y for emacs-orgmode@gnu.org; Sat, 01 Dec 2018 14:23:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gTArO-0005iq-DK for emacs-orgmode@gnu.org; Sat, 01 Dec 2018 14:23:26 -0500 Received: from mail-yw1-xc33.google.com ([2607:f8b0:4864:20::c33]:46876) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gTArO-0005iR-0K for emacs-orgmode@gnu.org; Sat, 01 Dec 2018 14:23:26 -0500 Received: by mail-yw1-xc33.google.com with SMTP id t13so3792711ywe.13 for ; Sat, 01 Dec 2018 11:23:25 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org > (when (looking-at "[ \t]*#\\+BEGIN_\\S-+[ \t]+\\(\\S-+\\)") Sorry, it obviously should have been \\(.+\\) at the end. 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. This is in the same spirit than what it already do for the affiliated attrs_X element. 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. They would still have to parse :args exactly as they now parse :attrs_X, but there are helper functions for that task. The idea is that stuff that is very specific to a backend X would be in :attrs_X, but stuff that is related to what makes the block semantically special could be in :args. Nevertheless special blocks will probably be backend specific in most cases.