From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ista Zahn Subject: Re: Inline code :results replace not working Date: Mon, 10 Nov 2014 12:03:44 -0500 Message-ID: References: <545C987E.4020203@gmail.com> <87fvdtwfg3.fsf@nicolasgoaziou.fr> <8661enxvfi.fsf@example.com> <86mw7z4ag3.fsf@example.com> <86y4rj2tm1.fsf@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnsNt-0008Gw-Sr for emacs-orgmode@gnu.org; Mon, 10 Nov 2014 12:04:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XnsNs-0001xz-OB for emacs-orgmode@gnu.org; Mon, 10 Nov 2014 12:04:09 -0500 Received: from mail-oi0-x230.google.com ([2607:f8b0:4003:c06::230]:55713) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnsNs-0001xZ-K6 for emacs-orgmode@gnu.org; Mon, 10 Nov 2014 12:04:08 -0500 Received: by mail-oi0-f48.google.com with SMTP id x69so5615557oia.7 for ; Mon, 10 Nov 2014 09:04:04 -0800 (PST) In-Reply-To: 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: Andreas Leha , emacs-orgmode Mailinglist On Mon, Nov 10, 2014 at 11:23 AM, Charles C. Berry wrote: > On Mon, 10 Nov 2014, Andreas Leha wrote: [snip] > >>>> >>>> Nonetheless, from a literate programming perspective, I think that >>>> replaceable (and raw) inline results are definitely desirable. >>>> Regardless of the state of their implementation in orgmode right now. > > > +1. +1 from me as well. For exactly the reason Andreas illustrated I've given up on using inline results for the past year or so. Would be great to see this feature become usable by implementing a system for replacing them. -Ista > > I find myself writing an inline src block, then typing `C-c C-c C-x u' to > view and then remove the result, then revise, and repeat. I'd be happy to > just leave it in the document. > >>> >>> FWIW, I'm not -- yet? -- convinced we should see the results of inline >>> code blocks inlined in the paragraph (and I'm not sure either it does >>> not cause interpretation problems); but, for sure, I'd love to be able >>> to preview the value interactively, at least. >>> >>>> So, I do not doubt, that you and Nicolas are right with that >>>> replaceable inline results are not implemented and are -- from >>>> orgmodes perspective -- expected to be evaluated only during export. >>>> >>>> My message was meant more as a feature request saying that I consider >>>> replaceable inline results useful and would like to see them supported >>>> by org. >>> >>> >>> Could you better explain your statement: "Limiting the use of inline >>> code to eval-on-export-only renders all the org-babel-execute-subtree >>> and related functionality useless"? >>> >>> I'm not sure to fully understand your use-case. That'd certainly be >>> worth explaining why you think it must be changed in the first instance >>> if you'd like Eric or Nicolas (or someone else) to change that. >>> >> >> Consider this simple toy example. If you press 'C-c C-v s' in the >> subtree, the document is 'broken' for export. If you press 'C-c C-v s' >> twice or more the document is 'broken' even for display. >> > > [deleted ECM] > > It seems like implementing removable inline results cleanly is a nettlesome > issue. > > But with the recent implementation of `org-babel-inline-result-wrap' it > would be trivial to wrap results with something like "@@babel:%s@@", > which can be found and removed more reliably than "=%s=". > > On export, either the :back-end property of such export-snippets could be > revised to the backend in use by a parse-tree filter or the code in each > org--export-snippet could be revised to accept such snippets. > > There is still the matter of adding code to find and remove those snippets > where Nicolas pointed in ob-core.al. > > But it seems do-able. > > HTH, > > Chuck >