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: Sat, 14 Dec 2013 12:25:59 +0100 Message-ID: <87k3f7ad2w.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55011) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrnM1-00035f-QL for emacs-orgmode@gnu.org; Sat, 14 Dec 2013 06:26:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VrnLo-0007fI-SO for emacs-orgmode@gnu.org; Sat, 14 Dec 2013 06:25:53 -0500 Received: from mail-ea0-x22a.google.com ([2a00:1450:4013:c01::22a]:65165) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrnLo-0007eu-Jh for emacs-orgmode@gnu.org; Sat, 14 Dec 2013 06:25:40 -0500 Received: by mail-ea0-f170.google.com with SMTP id k10so1330713eaj.1 for ; Sat, 14 Dec 2013 03:25:39 -0800 (PST) In-Reply-To: <8761r14cjr.fsf@gmail.com> (Eric Schulte's message of "Fri, 06 Dec 2013 14:12:39 -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: >> 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)? Regards, -- Nicolas Goaziou