From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: non-space, paste, (???) character for inline results Date: Tue, 30 Jan 2018 10:15:02 +0100 Message-ID: <87k1vzogh5.fsf@nicolasgoaziou.fr> References: <15598.1517300960@minshall-apollo.minshall.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45005) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1egS0a-0001u4-Ge for emacs-orgmode@gnu.org; Tue, 30 Jan 2018 04:15:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1egS0Q-0001wY-QK for emacs-orgmode@gnu.org; Tue, 30 Jan 2018 04:15:16 -0500 Received: from relay2-d.mail.gandi.net ([2001:4b98:c:538::194]:44628) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1egS0Q-0001wD-Jv for emacs-orgmode@gnu.org; Tue, 30 Jan 2018 04:15:06 -0500 In-Reply-To: <15598.1517300960@minshall-apollo.minshall.org> (Greg Minshall's message of "Tue, 30 Jan 2018 13:59:20 +0530") 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" To: Greg Minshall Cc: Org Mode List Hello, Greg Minshall writes: > hi. thanks again for org-mode. > > having discovered this variable, i tend to run with > : #+bind: org-babel-inline-result-wrap "%s" > > but, at the same time, i'd often like to put some character(s) before or > after the result of some particular inline call, e.g., a dollar sign, a > percent, etc. > > i could, i suppose, rebind o-b-i-r-wrap around those calls, but... > > if one writes, e.g., $call_foo(), the call_foo() doesn't happen > (presumably isn't recognized). > > i've tried various constructs that might allow the evaluation to be > recognize the call, but "paste" the result in with no intervening space, > things like > : #+macro: null > : ${{{null}}}call_foo() > but to no avail. (in the above case, i'm assuming macro expansion > happens *before* inline calls -- as it should -- so the inline call > procedure sees, e.g., $call_foo() and, again, doesn't distinguish it.) > > does such a construct exist? if not, would it make sense (and be > possible, given the installed base!) to add some such? (if so, i'd > probably vote for {{{}}}, the "null" macro which, anyway, currently > isn't modified -- in my setup, anyway -- during export.) This is now fixed. Thank you. Regards, -- Nicolas Goaziou