emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [BUG?] Strange message in minibuffer while exporting into HTML
Date: Fri, 11 Oct 2013 09:32:12 +0200	[thread overview]
Message-ID: <86siw89sar.fsf@somewhere.org> (raw)
In-Reply-To: 20131011041111.GB943@smoon

Hello Vladimir,

Vladimir Lomov wrote:
> please consider this sample Org document (ex-call.org):
>
> #+TITLE: Example with CALL directive
> #+AUTHOR: Vladimir Lomov
> #+OPTIONS: num:nil
>
> * This is first section
>
> 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.
>
> At first I was puzzled what causes this message in that particular Org
> document, while rest my Org documents are exported to HTML just fine.
>
> After a while I tried to strip down that document to figure out what
> may cause that message. And seems that problem is in CALL strings.
>
> In that particural document I have several CALL directive, commenting
> out them (just added a ~#~ at beginning of a line with a space after
> it) allows me to export that document into HTML.
>
> The purpose of this example document to ensure that even simple CALL
> line could cause such behaviour.
>
> This is CALL directive, it calls function defined below
> #+CALL: simple-func()
>
> Even without evaluation of this directive exporting into HTML fails
> with above message.
>
> Commenting that directive make it possible to export into HTML.
>
> Another attempt:
> #+CALL: simple-func(name="Vladimir Lomov")
>
> * The simple Emacs Lisp function
>
> This simple Emacs Lisp function has to be called by CALL directive:
> #+NAME: simple-func
> #+BEGIN_SRC emacs-lisp :var name="My name"
>   (format "[You told me:] %S" name)
> #+END_SRC
>
> My system:
> - Archlinux x86_64, gcc 4.8.1, make 4.0
> - emacs: GNU Emacs 24.3.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.0) of 2013-10-10 on smoon4
>   (compile from bzr trunk, revno 114606)
> - org-mode: Org-mode version 8.2.1 (release_8.2.1-77-g8aaf3c @ /usr/share/emacs/site-lisp/org/)
>
> I have typed above document in Emacs run as
> emacs -Q -l min-org.el --eval "(require 'ox-html)" ex-call.org
>
> Is this really a bug or my misunderstanding of 'CALL' directive usage?

I confirm the problem on my Windows environment:

- GNU Emacs 24.3.50.1 (i686-pc-mingw32) of 2013-09-30 on LEG570
- Org-mode version 8.1.1 (release_8.1.1-13-ga1f9a1)

... and I don't see any problem with your syntax. I'm as puzzled as you are.

Would you wanna help, I think trying to bisect Org mode would be a great step
into fixing what I think to be a problem in Org.

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2013-10-11  7:32 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 [this message]
2013-10-11  8:47   ` Vladimir Lomov
2013-10-11  7:45 ` Eric S Fraga
2013-10-11 11:38   ` Vladimir Lomov

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=86siw89sar.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).