all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Eric Schulte <schulte.eric-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] Bug when updating the hash: meta-lines get deleted
Date: Fri, 13 Dec 2013 20:59:33 +0100	[thread overview]
Message-ID: <86zjo44j4q.fsf@somewhere.org> (raw)
In-Reply-To: <87iousmtqe.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Eric Schulte's message of "Fri, 13 Dec 2013 12:33:13 -0700")

Hello Eric,

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.

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2013-12-13 19:59 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86zjo44j4q.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    --cc=schulte.eric-Re5JQEeQqe8AvxtiuMwx3w@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.