From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [PATCH] inline src block results can be removed Date: Sun, 16 Nov 2014 01:10:53 +0100 Message-ID: <87ppcoromq.fsf@nicolasgoaziou.fr> References: <87egt81acy.fsf@gmail.com> <8761ejq9ek.fsf@nicolasgoaziou.fr> <87sihltt3v.fsf@selenimh.mobile.lan> <877fyx1j15.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56182) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpnPx-0001Sp-3i for emacs-orgmode@gnu.org; Sat, 15 Nov 2014 19:10:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XpnPm-0002nQ-OU for emacs-orgmode@gnu.org; Sat, 15 Nov 2014 19:10:13 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:36527) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpnPm-0002lw-IT for emacs-orgmode@gnu.org; Sat, 15 Nov 2014 19:10:02 -0500 In-Reply-To: <877fyx1j15.fsf@gmail.com> (Aaron Ecay's message of "Fri, 14 Nov 2014 23:04:06 +0000") 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: "Charles C. Berry" Cc: mcg , Andreas Leha , emacs-orgmode@gnu.org, Ista Zahn Hello, Aaron Ecay writes: > This is a step back from the present situation, where a user can get > a custom format applied by default to all inline results by setting > =E2=80=98org-babel-inline-result-wrap=E2=80=99. I think it=E2=80=99s rea= sonable for users to > want to set off babel results in a special font (to indicate that > they are automatically generated, e.g.) This proposal would add an > additional overhead for generating this formatting to every inline > call. I expect Babel to provide a parameter to generate verbatim output, and a way to use this parameter globally. If it doesn't, then we can keep `org-babel-inline-result-wrap' and simply wrap {{{results(...)}}} macro around the output. > I think the method I sketched above will allow users to redefine the > results macro in the same way as any other macro (via #+MACRO), thus > allowing the possibility of user-specified special formatting. Babel output is expected to be modified by Babel functions/variables. I wouldn't want to see macro used as the main tool to modify inline Babel output. Of course, you can still do it. But you're on your own. {{{results(...)}}} is just a wrapper. > Indeed, this seems correct. (The =E2=80=9Cconst=E2=80=9D designation is = just a hint to > users/developers =E2=80=93 it doesn=E2=80=99t affect the ability of peopl= e who really > want to customize the value to setq it to something else in their init > file.) Of course, users are free to break their local copy of Org. >> With {{{results(@@backend:...@@)}}}, we don't need the extra trick. Even >> if it is more verbose, I think a regular syntax is better. > > This doesn=E2=80=99t mesh with the suggestion to allow the results macro = to > supply formatting. See above. Regards, --=20 Nicolas Goaziou