emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: asr@ufl.edu (Allen S. Rout)
To: emacs-orgmode@gnu.org
Subject: Re: Generic LaTeX class support (scrlttr2/isodoc)
Date: Wed, 09 Feb 2011 18:59:56 -0500	[thread overview]
Message-ID: <87fwrwyd1f.fsf@ufl.edu> (raw)
In-Reply-To: 87r5bi8cx5.fsf@ufl.edu

asr@ufl.edu (Allen S. Rout) writes:

> I'm trying to use your lisp to generate isodoc letters.  I'm wondering
> what tex processing commands you are using?

I'm closing in on the discrepancy. The exported TeX which Jambunathan
sent was 'similar' to what I'm getting, but there were a few important
differences.

Most importantly, I'm getting an additional newline between key and
value:

---
opening =

    My dear john
,
---
instead of 
---
opening =
    My dear john
,
---

This appears to fotch up the LaTex, and put those strings in a spot out
of the document entirely.


If I remove line 1137

	(insert	"\n")

from org-latex.el, this change in spacing goes away, but of course I
have no idea why it was put there.  Oddly, git-blame suggests that line
went in  in 2009, well before Jambunathan posted his isodoc files.

Does anyone who's been tinkering with the latex export code want to
expound on why that newline's in there?  Is it silly to just suggest
"Can we take it out?" 


- Allen S. Rout

      reply	other threads:[~2011-02-10  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 17:22 Generic LaTeX class support (scrlttr2/isodoc) Jambunathan K
2010-09-21 17:39 ` Jambunathan K
2011-02-08 20:54   ` Allen S. Rout
2011-02-09 23:59     ` Allen S. Rout [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=87fwrwyd1f.fsf@ufl.edu \
    --to=asr@ufl.edu \
    --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).