From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: non-space, paste, (???) character for inline results
Date: Wed, 31 Jan 2018 12:13:33 +0100
Message-ID: <87y3kewaaq.fsf@nicolasgoaziou.fr>
References: <87372nysl1.fsf@nicolasgoaziou.fr>
	<21575.1517361549@minshall-apollo.minshall.org>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51726)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1egqKl-0003eh-HT
	for emacs-orgmode@gnu.org; Wed, 31 Jan 2018 06:13:44 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1egqKg-00059J-Rf
	for emacs-orgmode@gnu.org; Wed, 31 Jan 2018 06:13:43 -0500
Received: from relay4-d.mail.gandi.net ([217.70.183.196]:37204)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1egqKg-000581-LW
	for emacs-orgmode@gnu.org; Wed, 31 Jan 2018 06:13:38 -0500
In-Reply-To: <21575.1517361549@minshall-apollo.minshall.org> (Greg Minshall's
	message of "Wed, 31 Jan 2018 06:49:09 +0530")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Greg Minshall <minshall@acm.org>
Cc: Org Mode List <emacs-orgmode@gnu.org>

Hello,

Greg Minshall <minshall@acm.org> writes:

> not wanting to look gift horses, etc., but i've a question.  if i
> understand the change correctly
> ----
> -             (looking-at "\\<call_\\([^ \t\n[(]+\\)[([]"))
> +             (looking-at "call_\\([^ \t\n[(]+\\)[([]"))
> ----
> now something like "oncall_foo()" will be taken as "on" followed by the
> inline results of call_foo().  is that right?  (testing, seems to be.)

Correct.

> i worry that might be a bit too lenient.

Note there is no such restriction on macros either, so you can write

  on{{{call}}}

If "call" macro expands to "call_foo()", you get a surprising error if
the inline call is not expanded thereafter.

> sometimes one might want "oncall_foo()" to stay as "oncall_foo()".

In this case, you can use verbatim markup, or even non-breaking space
before the underscore.

Whatever the regexp we use, some contexts will require non-breaking
space anyway. The current solution is at least consistent with other
parts of Org (e.g., macros).

WDYT?

Regards,

-- 
Nicolas Goaziou