From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] Bug when updating the hash: meta-lines get deleted
Date: Sat, 14 Dec 2013 09:28:53 +0100 [thread overview]
Message-ID: <86y53nzvi2.fsf@somewhere.org> (raw)
In-Reply-To: 87a9g4e3c4.fsf@gmail.com
Hello Eric,
Eric Schulte wrote:
> "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> writes:
>> Eric Schulte wrote:
>>>> When results caching is enabled, and when the hash must be updated, the
>>>> "meta-lines" in front of the results block are _deleted_.
>>>
>>> You should use a named code block if you want to decorate the results.
>>
>> No, as long as the lines which I do insert between the code block and
>> the results are of the type "#+...", you _don't_ need to name the block.
>>
>> Disable the caching, and see by yourself that you can insert such lines
>> without problems.
>>
>> This is something Nicolas did a couple of months ago, to avoid having to
>> name all the code blocks when they are semantically followed by their
>> results -- that is, such "#+..." lines are like ignored for the update.
>
> Alright, I just pushed up a fix for this issue. Please let me know if
> it continues to cause problems for you.
It does fix the problem. Thanks a lot for your prompt fix!
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2013-12-14 8:28 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
[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 [this message]
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=86y53nzvi2.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).