From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: words starting with call_ confuse C-c C-c and export Date: Sun, 15 Dec 2013 23:43:49 +0100 Message-ID: <87d2kxag62.fsf@gmail.com> References: <87ob4ytoqf.wl%n142857@gmail.com> <87zjohvem7.fsf@gmail.com> <87iov16b3d.fsf@gmail.com> <87wqjhu5i1.fsf@gmail.com> <8761r14cjr.fsf@gmail.com> <87k3f7ad2w.fsf@gmail.com> <878uvl3if1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51138) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VsKPT-0005pi-9x for emacs-orgmode@gnu.org; Sun, 15 Dec 2013 17:43:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VsKPK-00082J-S1 for emacs-orgmode@gnu.org; Sun, 15 Dec 2013 17:43:39 -0500 Received: from mail-ea0-x22a.google.com ([2a00:1450:4013:c01::22a]:62913) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VsKPK-00082E-Km for emacs-orgmode@gnu.org; Sun, 15 Dec 2013 17:43:30 -0500 Received: by mail-ea0-f170.google.com with SMTP id k10so1901258eaj.1 for ; Sun, 15 Dec 2013 14:43:29 -0800 (PST) In-Reply-To: <878uvl3if1.fsf@gmail.com> (Eric Schulte's message of "Sun, 15 Dec 2013 14:37:06 -0700") 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: Eric Schulte Cc: emacs-orgmode@gnu.org Hello, Eric Schulte writes: > Nicolas Goaziou writes: >> In fact, they are already mandatory. The problem is different. Current >> regexp is: >> >> "\\([^\n]*?\\)call_\\([^()\n]+?\\)\\(\\[\\(.*?\\)\\]\\|\\(\\)\\)(\\([^\n]*?\\))\\(\\[\\(.*?\\)\\]\\)?" >> >> In particular, name is \\([^()\n]+?\\), and can include whitespace >> characters. Therefore "call_name (args)" is valid. Isn't it too much >> permissive in the context of an Org (i.e. textual) document? >> >> Also, couldn't we limit names to alphanumeric characters and, maybe, >> some puctuation (e.g. hypen)? >> > > Why don't we exclude whitespace from names. Do you think that would be > sufficient? It would solve the current problem, but there are still many problematic characters allowed (e.g., commas, curly brackets). I think there's no point in allowing "call_{i=1}()" as a valid inline Babel call. Furthermore, I don't think it's a real limitation to use alphanumeric characters (and hyphen) only for a function name. I would even require an alphabetic character as the first char, to avoid calls like: "call_1()". BTW, later in that regexp, there is a dubious "(\\([^\n]*?\\))". Is there any reason not to use "(\\(.*?\\))" instead? Also, what about the empty matcher "\\(\\)"? I don't get its use. Regards, -- Nicolas Goaziou