From: Vladimir Lomov <lomov.vl@gmail.com>
To: General discussions about Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG?] Strange message in minibuffer while exporting into HTML
Date: Fri, 11 Oct 2013 20:38:52 +0900 [thread overview]
Message-ID: <20131011113852.GI943@smoon> (raw)
In-Reply-To: <8761t42quy.fsf@ucl.ac.uk>
Hello,
** Eric S Fraga [2013-10-11 08:45:09 +0100]:
> Vladimir Lomov <lomov.vl@gmail.com> writes:
>> Hello,
>> please consider this sample Org document (ex-call.org):
> [...]
>> Recently I faced with a strange message in minibuffer:
>> #+BEGIN_EXAMPLE
>> Marker points into wrong buffer: #<marker in no buffer>
>> #+END_EXAMPLE
>> when exporting the Org document into HTML.
> [...]
> I think this might be a is the same problem I posted about a couple of days ago, a
> problem that affects both #+call: and call_ invocations of babel blocks.
> When I try your file, exporting to either HTML or LaTeX, I get the same
> error. I am using the latest emacs snapshot.
> What is interesting is that if I save your file as t.org, extra buffers
> named t.org<2> and t.org<2><2> are created after having done two export
> attempts. Do either of these appear for you?
No, I think because export function fails so it can't produce any buffer.
> By the way, what version of Emacs are you using?
Emacs compile from bzr repository (currently this is 114588).
---
WBR, Vladimir Lomov
--
"For three days after death hair and fingernails continue to grow but
phone calls taper off."
-- Johnny Carson
prev parent reply other threads:[~2013-10-11 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 4:11 [BUG?] Strange message in minibuffer while exporting into HTML Vladimir Lomov
2013-10-11 4:32 ` Vladimir Lomov
2013-10-11 7:32 ` Sebastien Vauban
2013-10-11 8:47 ` Vladimir Lomov
2013-10-11 7:45 ` Eric S Fraga
2013-10-11 11:38 ` Vladimir Lomov [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=20131011113852.GI943@smoon \
--to=lomov.vl@gmail.com \
--cc=emacs-orgmode@gnu.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).