From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inline code :results replace not working
Date: Mon, 10 Nov 2014 08:23:14 -0800 [thread overview]
Message-ID: <alpine.OSX.2.00.1411100759470.428@charles-berrys-macbook.local> (raw)
In-Reply-To: <oluh9y7e0z5.fsf@med.uni-goettingen.de>
On Mon, 10 Nov 2014, Andreas Leha wrote:
> Hi Sebastien,
>
> Sebastien Vauban <sva-news@mygooglest.com> writes:
>> Andreas Leha wrote:
>>> Sebastien Vauban <sva-news@mygooglest.com> writes:
>>>> Andreas Leha wrote:
>>>>>> For me, that's the correct behavior, as inline code blocks are
>>>>>> *only expected to be evaluated during export*.
>>>>>
>>>>> I disagree here.
>>>>
[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.
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-<backend>-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
next prev parent reply other threads:[~2014-11-10 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:01 Inline code :results replace not working mcg
2014-11-08 21:27 ` Nicolas Goaziou
2014-11-10 9:21 ` Sebastien Vauban
2014-11-10 9:40 ` Andreas Leha
2014-11-10 10:27 ` Sebastien Vauban
2014-11-10 10:56 ` Andreas Leha
2014-11-10 11:16 ` Sebastien Vauban
2014-11-10 11:42 ` Andreas Leha
2014-11-10 16:23 ` Charles C. Berry [this message]
2014-11-10 17:03 ` Ista Zahn
2014-11-10 20:04 ` Grant Rettke
2014-11-10 20:45 ` Thomas S. Dye
2014-11-10 21:26 ` Grant Rettke
2014-11-11 1:53 ` Ista Zahn
2014-11-11 14:37 ` Grant Rettke
2014-11-13 18:40 ` Michael
2014-11-14 15:11 ` Grant Rettke
2014-11-12 9:03 ` Sebastien Vauban
2014-11-12 17:26 ` Charles Berry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.OSX.2.00.1411100759470.428@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).