emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Yasushi SHOJI <yashi@atmark-techno.com>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] [babel] repeated exports w/ inline src blocks yield different results
Date: Wed, 27 Nov 2013 11:27:17 +0900	[thread overview]
Message-ID: <87a9gqziii.wl@dns1.atmark-techno.com> (raw)
In-Reply-To: <loom.20131124T044020-399@post.gmane.org>

At Sun, 24 Nov 2013 04:18:38 +0000 (UTC),
Charles Berry wrote:
> and you see the extra '#+END_SRC' line.
> And if you keep repeating those keystrokes, the second result again appears.
> However, sometimes a minor change and then an erasure (perhaps 'a a C-x u')
> followed by the export keystrokes yields the correct result.

It seems like a cache issue.  `org-element-cache-reset' before exporting
corrects the result on my system.

still learning how the cache works...

  reply	other threads:[~2013-11-27  2:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24  4:18 [bug] [babel] repeated exports w/ inline src blocks yield different results Charles Berry
2013-11-27  2:27 ` Yasushi SHOJI [this message]
2013-11-28 21:31   ` Nicolas Goaziou

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:

  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=87a9gqziii.wl@dns1.atmark-techno.com \
    --to=yashi@atmark-techno.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).