From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] Simplify attributes syntax Date: Sat, 09 Mar 2013 22:19:05 +0100 Message-ID: <87hakki852.fsf@gmail.com> References: <87ppz9zar8.fsf@gmail.com> <87hakkcpq2.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 ([208.118.235.92]:35149) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UERAl-0000pv-71 for emacs-orgmode@gnu.org; Sat, 09 Mar 2013 16:19:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UERAk-0008LO-0S for emacs-orgmode@gnu.org; Sat, 09 Mar 2013 16:19:19 -0500 Received: from mail-wg0-f43.google.com ([74.125.82.43]:36644) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UERAj-0008LK-QK for emacs-orgmode@gnu.org; Sat, 09 Mar 2013 16:19:17 -0500 Received: by mail-wg0-f43.google.com with SMTP id e12so3764898wge.10 for ; Sat, 09 Mar 2013 13:19:17 -0800 (PST) In-Reply-To: <87hakkcpq2.fsf@gmail.com> (Aaron Ecay's message of "Sat, 09 Mar 2013 14:55:49 -0500") 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: Org Mode List Hello, Aaron Ecay writes: > I think this patch is a welcome simplification. Would it be possible to > merge the code that is used for reading babel header args (things like > =E2=80=9C:results output :file foo.txt=E2=80=9D) with the code from the e= xporter? It is probably possible, but that's way beyond the scope of this patch. Note that the needs are very different for each reader. Export reader must be very simple (no escaping character) and only needs to read strings. OTOH Babel reader has to determine the type of data it reads (list, number...). > Unless they are parsed by the same code, the two syntaxes will differ in > subtle and headache-inducing ways (for users and developers). It can be troublesome for users in some corner cases (I think Babel reader uses "none" or "no" where Export reader expects "nil"). I doubt it will be for developers, who should know which reader they are working with. I could replace "nil" -> nil with "no" -> nil in the Export reader, but I don't like this solution. In English, there are "no", "No", "NO", "None", "NONE", "none"... but in Elisp, there is only "nil". Regards, --=20 Nicolas Goaziou