emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: zwz <zhangweize@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: BUG: footnote conflicts with code export to pdf
Date: Mon, 24 Oct 2011 14:23:06 +0800	[thread overview]
Message-ID: <87lisa3o39.fsf@gmail.com> (raw)
In-Reply-To: 4020.1319338944@alphaville.dokosmarshall.org

Nick Dokos <nicholas.dokos@hp.com> writes:

> zwz <zhangweize@gmail.com> wrote:
>> Steps to reproduce it:
>> This org file can be exported to pdf correctly.
>> #+begin_src org
>> * test
>>   #+BEGIN_SRC c
>>   void main(){
>>     int a;
>>   }
>>   #+END_SRC
>> #+end
>> Then you modify it:
>> #+begin_src org
>> * test
>>   #+BEGIN_SRC c
>>   void main(){
>>     int a[5];
>>   }
>>   #+END_SRC
>> #+end
>> It says "org-export-latex-preprocess: Wrong type argument: stringp,
> nil"
>> when you try to export the file.
> You didn't say what version of org you are using. I cannot reproduce it
> in Org-mode version 7.7 (release_7.7.416.g93bd.dirty)
> Nick

I am using org-mode 7.7-1 (installed by pacman on Archlinux).

  reply	other threads:[~2011-10-24  6:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-23  2:55 BUG: footnote conflicts with code export to pdf zwz
2011-10-23  3:02 ` Nick Dokos
2011-10-24  6:23   ` zwz [this message]
2011-10-24 19:01     ` Nick Dokos
2011-10-25 13:54       ` zwz

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