From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] [PATCH] [parser] org-element.el: Handle block parameters Date: Wed, 30 Oct 2013 09:01:06 +0100 Message-ID: <87iowfb325.fsf@gmail.com> References: <1382987074-19223-1-git-send-email-aaronecay@gmail.com> <878uxca3p6.fsf@gmail.com> <8738njcrgl.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56379) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VbQi3-0004jd-3G for emacs-orgmode@gnu.org; Wed, 30 Oct 2013 04:01:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VbQhu-0002Tn-Mf for emacs-orgmode@gnu.org; Wed, 30 Oct 2013 04:00:59 -0400 Received: from mail-wg0-x230.google.com ([2a00:1450:400c:c00::230]:35736) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VbQhu-0002TU-FX for emacs-orgmode@gnu.org; Wed, 30 Oct 2013 04:00:50 -0400 Received: by mail-wg0-f48.google.com with SMTP id b13so907711wgh.3 for ; Wed, 30 Oct 2013 01:00:49 -0700 (PDT) Received: from selenimh ([91.224.148.150]) by mx.google.com with ESMTPSA id fb4sm12888760wib.8.2013.10.30.01.00.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Oct 2013 01:00:48 -0700 (PDT) In-Reply-To: <8738njcrgl.fsf@gmail.com> (Aaron Ecay's message of "Wed, 30 Oct 2013 00:28:42 -0400") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hello, Aaron Ecay writes: > I have several export filters which translate special blocks into latex > code (doing some tedious string munging in elisp, such that a simple > latex block is not warranted; I also have the eventual goal of making > them cross-backend, which will involve a different bit of tedious > munging). These filters take arguments in the #+begin_foo line. IIRC, I already suggested a solution with Babel for this problem. There's no need to complicate core Org syntax for such a specific case. > I also think it would be nice for the org code following this paragraph > to be translated to output that makes sense for each backend, with the > quote=E2=80=99s author formatted nicely (on a new line preceded by a dash, > aligned to the right margin in text/html, using the csquotes package in > latex, etc.). This patch would enable such a functionality. > > #+begin_quote Chico Marx > Why a duck? > #+end_quote Well actually, this kind of syntax is confusing at best. Something like the following could be used instead: #+begin_quote :author Chico Marx Actually, there are two points to consider: 1. Providing something like :author implies that all back-ends in core and contrib and the manual have to be updated accordingly. 2. "parameters" is too vague to be useful. It needs to be parsed further, which means that we must define explicitly use cases and keywords. Thus, I don't think adding "parameters" to every block is a good move if we don't know beforehand how they will be used. Though, it is possible to extend the syntax to well-defined specific cases. :author may be one of them, there are certainly others. Regards, --=20 Nicolas Goaziou