emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] in org-element-link-parser (lilypond file does not export to latex)
Date: Sat, 01 Mar 2014 10:12:28 +0100	[thread overview]
Message-ID: <87k3ce470j.fsf@gmail.com> (raw)
In-Reply-To: 87zjlapc38.fsf@gmail.com

Nicolas Goaziou <n.goaziou@gmail.com> writes:

Hello,

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> when trying to export this example lilypond file
>>
>> https://raw.github.com/mjago/ob-lilypond/master/examples/basic-mode/pdf-example/pdf-example.org
>>
>> to LaTeX (C-c C-e l L) I hit the following error:
>>
>> ,----------------------------------------------
>> | Wrong type argument: integer-or-marker-p, nil
>> `----------------------------------------------
>
> I cannot reproduce it. OTOH, I don't have Lilypond installed.
>
>> It turns out that org-element tries to parse a link but 
>>
>> ,----------------------------------
>> | (defun org-element-link-parser ()
>> |   "Parse link at point.
>> `----------------------------------
>
> Could you provide an ECM, that is the exact link generating this error?


This is the first code block of the original .org file with one link
(that could not be exported really, because it was evaluated on
another machine so the eps did not really exist on my machine. But the
org parser choked with this kind of result-links:

#+begin_src org
#+TITLE: Modes in the Key of C
#+DATE:
#+OPTIONS: timestamp:nil num:nil toc:nil 
#+LaTeX_HEADER: \usepackage[cm]{fullpage}
* Ionian Mode
Lorem ipsum dolor sit amet
#+LaTeX: \linebreak
#+ATTR_LaTeX: width=17cm 
#+begin_src lilypond :file ionian.eps :noweb yes

  <<version-and-paper>>
  \relative c' { 
    c d e f g a b c b a g f e d c d  
    e f g a b c b a g f e d c1
}
#+end_src

#+results[0c21e5c5bd30d880d2bd230aa09b7613c2554835]:
[[file:ionian.eps]]
#+end_src

Here is what I get when I delete the above result link and evaluate
the code-block on my machine - this parses and exports fine:

#+begin_src org
#+TITLE: Modes in the Key of C
#+DATE:
#+OPTIONS: timestamp:nil num:nil toc:nil 
#+LaTeX_HEADER: \usepackage[cm]{fullpage}

* Ionian Mode
Lorem ipsum dolor sit amet
#+LaTeX: \linebreak
#+ATTR_LaTeX: width=17cm 
#+begin_src lilypond :file ionian.eps :noweb yes

  <<version-and-paper>>
  \relative c' { 
    c d e f g a b c b a g f e d c d  
    e f g a b c b a g f e d c1
}
#+end_src

#+results:
[[file:ionian.eps]]
#+end_src

-- 
cheers,
Thorsten

  reply	other threads:[~2014-03-01  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01  1:17 [BUG] in org-element-link-parser (lilypond file does not export to latex) Thorsten Jolitz
2014-03-01  8:17 ` Nicolas Goaziou
2014-03-01  9:12   ` Thorsten Jolitz [this message]
2014-03-01 11:40     ` Nicolas Goaziou
2014-03-01 11:58       ` Thorsten Jolitz

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=87k3ce470j.fsf@gmail.com \
    --to=tjolitz@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).