emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Grant Rettke <gcr@wisdomandwonder.com>
To: Ista Zahn <istazahn@gmail.com>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>,
	emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>,
	"Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: Inline code :results replace not working
Date: Mon, 10 Nov 2014 14:04:15 -0600	[thread overview]
Message-ID: <CAAjq1mct3e1zMf0=P8uVuUSKcfYVV=7VKg7SSFr9XYFu-0SbEQ@mail.gmail.com> (raw)
In-Reply-To: <CA+vqiLHvQdcU9Xynf-vWqN+yG7pk47jTpv4A5oqG3RK=0q1AUw@mail.gmail.com>

On Mon, Nov 10, 2014 at 11:03 AM, Ista Zahn <istazahn@gmail.com> wrote:
> On Mon, Nov 10, 2014 at 11:23 AM, Charles C. Berry <ccberry@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.

  reply	other threads:[~2014-11-10 20:04 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 [this message]
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='CAAjq1mct3e1zMf0=P8uVuUSKcfYVV=7VKg7SSFr9XYFu-0SbEQ@mail.gmail.com' \
    --to=gcr@wisdomandwonder.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --cc=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=istazahn@gmail.com \
    /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).