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: Mon, 16 Dec 2013 17:58:42 +0100 Message-ID: <878uvkag1p.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42310) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VsbV3-0006uj-5x for emacs-orgmode@gnu.org; Mon, 16 Dec 2013 11:58:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VsbUu-0001Jf-Q8 for emacs-orgmode@gnu.org; Mon, 16 Dec 2013 11:58:33 -0500 Received: from mail-ea0-x22a.google.com ([2a00:1450:4013:c01::22a]:59552) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VsbUu-0001JS-J4 for emacs-orgmode@gnu.org; Mon, 16 Dec 2013 11:58:24 -0500 Received: by mail-ea0-f170.google.com with SMTP id k10so2390064eaj.1 for ; Mon, 16 Dec 2013 08:58:23 -0800 (PST) In-Reply-To: <87wqj425kk.fsf@gmail.com> (Eric Schulte's message of "Mon, 16 Dec 2013 08:12:11 -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: >> It would solve the current problem, but there are still many problematic >> characters allowed (e.g., commas, curly brackets). I think there's no >> point in allowing "call_{i=1}()" as a valid inline Babel call. >> >> Furthermore, I don't think it's a real limitation to use alphanumeric >> characters (and hyphen) only for a function name. I would even require >> an alphabetic character as the first char, to avoid calls like: >> "call_1()". >> > > I often use "/" in function names, and in general I'd prefer not to > remove characters (e.g., "{") unless there is a specific reason. I think there's a specific reason to disallow naming a function "{i=1}": it is too close to underline syntax. We should make syntax less prone to ambiguity (see recent thread about underline and subscript) ; this doesn't help. Think also about call_~my-verbatim-function-name~(), call_@@latex:my-export-snippet@@()... 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. I suggest to select a few symbols allowed in names (e.g., "/") as a starter. It is always possible to discuss on a case by case basis if other symbols should be added. Regards, -- Nicolas Goaziou