From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Bug when updating the hash: meta-lines get deleted
Date: Fri, 13 Dec 2013 12:33:13 -0700 [thread overview]
Message-ID: <87iousmtqe.fsf@gmail.com> (raw)
In-Reply-To: <86txedkn3o.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 13 Dec 2013 12:27:07 +0100")
You should use a named code block if you want to decorate the results.
Best,
"Sebastien Vauban" <sva-news@mygooglest.com> writes:
> Hello,
>
> When results caching is enabled, and when the hash must be updated, the
> "meta-lines" in front of the results block are _deleted_.
>
> Such meta-lines include:
> - ATTR_LaTeX lines
> - BEGIN/END_CENTER environments
>
> ECM:
>
> --8<---------------cut here---------------start------------->8---
> #+PROPERTY: cache yes
>
> #+begin_src R
> print("Hello")
> #+end_src
>
> #+ATTR_LaTeX: {\tiny
> #+results[824ca019826a9f384bd35371065bb2418a1afedf]:
> : Hello
> #+ATTR_LaTeX: }
> --8<---------------cut here---------------end--------------->8---
>
> If you change the source code block (such a setting the string to
> "Hello2"), you get the following Org buffer:
>
> --8<---------------cut here---------------start------------->8---
> #+PROPERTY: cache yes
>
> #+begin_src R
> print("Hello2")
> #+end_src
>
> #+results[663ebd0c20f3ed9105d254971336679e44354a3e]:
> : Hello2
>
> #+ATTR_LaTeX: }
> --8<---------------cut here---------------end--------------->8---
>
> Best regards,
> Seb
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2013-12-13 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 11:27 [babel] Bug when updating the hash: meta-lines get deleted Sebastien Vauban
2013-12-13 19:33 ` Eric Schulte [this message]
[not found] ` <87iousmtqe.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-13 19:59 ` Sebastien Vauban
2013-12-13 22:11 ` Eric Schulte
2013-12-14 8:28 ` Sebastien Vauban
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=87iousmtqe.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sva-news@mygooglest.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).