emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Maus <dmaus@ictsoc.de>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Fail to compile a file's LaTeX export
Date: Sat, 20 Mar 2010 22:40:30 +0100	[thread overview]
Message-ID: <87bpei1xkh.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <m1pr2ywujj.fsf@cam.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1815 bytes --]

Leo wrote:
>On 2010-03-20 20:29 +0000, Leo wrote:
>> Hello,
>>
>> While taking some common lisp notes, I found compiling the following org
>> file's LaTeX output fails.
>>
>> --------------------------------
>> #+title: test file
>>
>> * one
>>   1. (char "string" 2) => #\r
>>   2. define-modify-macro
>>   3. (code-char 66) => #\B and (char-code #\B) => 66
>>   4. terpri and fresh-line
>>   5. "~n&" print a new line if not at the beginning of a line and then n-1 new lines.
>> --------------------------------
>>
>> Leo

>BTW, this was tested with the devel version of org.

Can confirm this for

Org-mode version 6.34trans (release_6.34c.225.g1576)

on

GNU Emacs 24.0.50.1 (i486-pc-linux-gnu, GTK+ Version 2.18.7) of
 2010-03-11 on elegiac, modified by Debian

Exporting to LaTeX works fine but compiling the LaTeX file errors out
with:

,----
| ERROR: LaTeX Error: Something's wrong--perhaps a missing \item.
|
| --- TeX said ---
|
| See the LaTeX manual or LaTeX Companion for explanation.
| Type  H <return>  for immediate help.
|  ...
|
| l.37 \item
|            define-modify-macro
| --- HELP ---
| The most probable cause is an omitted \item command in a list-making
| environment. It is also caused by forgetting the argument of a
| thebibliography environment.
`----

Where the LaTeX code for the enumerate environment reads:

,----
| \begin{enumerate}
| \item (char ``string'' 2) => \#\r
| \item define-modify-macro
| \item (code-char 66) => \#\B and (char-code \#\B) => 66
| \item terpri and fresh-line
| \item ``\~{}n\&'' print a new line if not at the beginning of a line and then n-1 new lines.
| \end{enumerate}
`----

I suppose the \#\r is the problematic piece, will look into it tomorow.

HTH
 -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-03-20 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20 20:29 Fail to compile a file's LaTeX export Leo
2010-03-20 21:30 ` Leo
2010-03-20 21:40   ` David Maus [this message]
2010-03-21  4:24     ` Tim Burt
2010-03-21  6:30 ` Carsten Dominik

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=87bpei1xkh.wl%dmaus@ictsoc.de \
    --to=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=sdl.web@gmail.com \
    /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).