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: Thu, 06 Mar 2014 15:12:51 -0700 Message-ID: <87mwh3t1jj.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43459) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLgdU-0002nl-Tb for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 17:19:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLgdO-00064w-Oi for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 17:19:28 -0500 Received: from mail-pd0-x236.google.com ([2607:f8b0:400e:c02::236]:56755) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLgdO-00064n-IR for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 17:19:22 -0500 Received: by mail-pd0-f182.google.com with SMTP id g10so3149142pdj.13 for ; Thu, 06 Mar 2014 14:19:21 -0800 (PST) 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: > >>> 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. > 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. Best, > > 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, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D