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: Mon, 10 Mar 2014 08:44:31 -0600 Message-ID: <87fvmqkt9s.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WN1TT-0000f1-K6 for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 10:46:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WN1TO-0004x2-Em for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 10:46:39 -0400 Received: from mail-pa0-x231.google.com ([2607:f8b0:400e:c03::231]:63225) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WN1TO-0004wr-8B for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 10:46:34 -0400 Received: by mail-pa0-f49.google.com with SMTP id lj1so7327910pab.36 for ; Mon, 10 Mar 2014 07:46:33 -0700 (PDT) In-Reply-To: <87r46a2kmw.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 10 Mar 2014 15:28:23 +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: > >>> We're talking about function names, not free-form text, so limitations >>> are understandable. For example, macro names only allow alphanumeric >>> characters or hyphens and have to start with an alphabetic character. >> >> Having considered this, unless there are user objections I'd be happy >> limiting function names to the same restricted alphabet as macro names. >> >> This would be a breaking change though, and should be mentioned as such >> in the notes. > > Once you have settled for a regexp (do you want to include "/" > character?), please let me know, I'll update org-element accordingly. > Is "/" allowed in macro names? 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? > > Regards, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D