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 21:49:33 +0100 Message-ID: <87iork1mw2.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> <87a9cw3jwa.fsf@gmail.com> <87iorkn2x2.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50215) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNTc0-0007GL-KS for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 16:49:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WNTbo-0004fc-U0 for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 16:49:20 -0400 Received: from mail-wi0-x22f.google.com ([2a00:1450:400c:c05::22f]:58034) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNTbo-0004fY-Mf for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 16:49:08 -0400 Received: by mail-wi0-f175.google.com with SMTP id cc10so1498258wib.14 for ; Tue, 11 Mar 2014 13:49:07 -0700 (PDT) In-Reply-To: <87iorkn2x2.fsf@gmail.com> (Eric Schulte's message of "Tue, 11 Mar 2014 09:57:45 -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 Eric Schulte writes: >> 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. >> > > I think it is more important that code block names resemble data names > than macro names, so I'm afraid that I'm back to my original position of > preferring to keep as many characters as possible in function names. You can still have forbidden characters even with the current permissive regexp: #+NAME: how do you call me? is a valid NAME value but not a valid Babel name. Another option is, as noted before, to restrict NAME values accordingly. Regards, -- Nicolas Goaziou