From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: words starting with call_ confuse C-c C-c and export Date: Sun, 15 Dec 2013 14:37:06 -0700 Message-ID: <878uvl3if1.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41523) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VsJOO-0000W1-UK for emacs-orgmode@gnu.org; Sun, 15 Dec 2013 16:38:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VsJOJ-0007sT-La for emacs-orgmode@gnu.org; Sun, 15 Dec 2013 16:38:28 -0500 Received: from mail-pd0-x22c.google.com ([2607:f8b0:400e:c02::22c]:51013) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VsJOJ-0007sN-EQ for emacs-orgmode@gnu.org; Sun, 15 Dec 2013 16:38:23 -0500 Received: by mail-pd0-f172.google.com with SMTP id g10so4537939pdj.3 for ; Sun, 15 Dec 2013 13:38:22 -0800 (PST) In-Reply-To: <87k3f7ad2w.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 14 Dec 2013 12:25:59 +0100") 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Hello, > > Eric Schulte writes: > >> Nicolas Goaziou writes: > >>> Just to be clear, I thought about making parens mandatory in inline >>> Babel call syntax. Underscore is overloaded already: underline, >>> subscript... >>> >> >> I'm open to this change. > > 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? -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D