From: Michael <giepen.m@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Inline code :results replace not working
Date: Thu, 13 Nov 2014 18:40:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20141113T192515-378@post.gmane.org> (raw)
In-Reply-To: CA+vqiLFBxVTRgYKeRaH-rsd-Xpt9V++c+gtUYEPfBEgPOCULbA@mail.gmail.com
Ista Zahn <istazahn <at> gmail.com> writes:
>
> On Mon, Nov 10, 2014 at 3:04 PM, Grant Rettke <gcr <at>
wisdomandwonder.com> wrote:
> > On Mon, Nov 10, 2014 at 11:03 AM, Ista Zahn <istazahn <at> gmail.com>
wrote:
> >> On Mon, Nov 10, 2014 at 11:23 AM, Charles C. Berry <ccberry <at>
ucsd.edu> 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.
> >
> > My approach here has been to use "hidden" source blocks that aren't
> > exported but make it
> > really easy to see the result during development. These settings
> > should work on any configuration,
> > so I didn't include mine here.
> >
> > ✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂
> > #+BEGIN_SRC R
> > a = 10
> > b = 23
> > c = a + b
> > #+END_SRC
> >
> > #+BEGIN_SRC R :results output silent :exports none
> > c
> > #+END_SRC
> >
> > The user calculated src_R{c}.
> > ✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂✂
> >
> > When you use these functions
> > http://orgmode.org/manual/Key-bindings-and-useful-functions.html#Key-
bindings-and-useful-functions
> > the addition of these "hidden" blocks hav almost zero cost and give me
> > what I want.
>
> The problem I have is not that I miss being able to see results of the
> inline block in the org-mode buffer. The problem is that I don't want
> blocks to be evaluated on export (too time consuming in many cases).
> So I turn that off, and either evaluate the blocks one at a time (I'm
> aware of the dangers of this, not my point here) or call
> org-babel-execute-buffer. Everytime I do that I get duplicate output
> from inline code. As far as I can see inline code +
> org-babel-execute-buffer is incompatible, which is why I gave up on
> the former.
>
> Best,
> Ista
>
>
+1
First of all nice that something is "happening" on the issue - happy not to
be the only one missing something.
+ 1
on I also don't bother too much about the eval-on-export functionality as
long as I can evaluate the buffer and get non repeated inline results.
For now I don't use inline blocks anymore.
As an intermediate solution I would like to specify document wide options
for inline code blocks only (:results silent); sorry - cannot find the
example I saw on the net recently on how to do so. I could not get it
working.
I could set results silent argument in every inline src code but don't want
the inline source code to be too long unnecessarily (affects readability of
text).
next prev parent reply other threads:[~2014-11-13 18:45 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
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 [this message]
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=loom.20141113T192515-378@post.gmane.org \
--to=giepen.m@gmail.com \
--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).