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: Tue, 11 Mar 2014 15:11:17 +0100 Message-ID: <87a9cw3jwa.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> <87d2kxag62.fsf@gmail.com> <87wqj425kk.fsf@gmail.com> <878uvkag1p.fsf@gmail.com> <87mwh3t1jj.fsf@gmail.com> <87r46a2kmw.fsf@gmail.com> <87fvmqkt9s.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49147) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNNOV-0001Ij-VW for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 10:11:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WNNON-0007bR-Ig for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 10:10:59 -0400 Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:42200) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNNON-0007bJ-CE for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 10:10:51 -0400 Received: by mail-wg0-f46.google.com with SMTP id b13so4030134wgh.5 for ; Tue, 11 Mar 2014 07:10:50 -0700 (PDT) In-Reply-To: <87fvmqkt9s.fsf@gmail.com> (Eric Schulte's message of "Mon, 10 Mar 2014 08:44:31 -0600") 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: > Is "/" allowed in macro names? No. Macro names use the following regexp: [a-zA-Z][-a-zA-Z0-9_]* > I think the biggest benefit here is > unification between macro and function names. Is there a macro name > regexp which could be used directly (to ensure that these two stay > unified)? I don't see one, so I expect we'll want to add an > org-babel-function-name regexp along the lines of "[a-zA-Z0-9\-\/]+". > This would then be used in the following variables. > - org-babel-src-block-regexp > - org-babel-src-name-w-name-regexp > > And the following functions should be updated to ensure that the name > only includes the allowed characters. > - org-babel-named-data-regexp-for-name > - org-babel-named-src-block-regexp-for-name > > Does this sound about right? Note there is no limitation on the contents of NAME keywords. Unless the same limitation propagates to those (but should it?), Babel calls will be ignored if forbidden characters are used. Regards, -- Nicolas Goaziou