emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: Latex export bugs and a request
Date: Wed, 18 Mar 2009 11:33:09 -0500	[thread overview]
Message-ID: <87bpryeqpm.fsf@fastmail.fm> (raw)
In-Reply-To: <4CCC1BE5-B46F-4A01-AB69-AB1A28F4FF86@uva.nl> (Carsten Dominik's message of "Mon, 16 Mar 2009 22:16:48 +0100")

Hi Carsten,

Carsten Dominik <dominik@science.uva.nl> writes:

> Strange, I am getting {lll}, with no vertical lines on either outside.
> Ah, you have org-export-latex-tables-column-borders turned on.
> Yes, there was a bug, fixed now.  Thanks!

Thanks! Works beautifully now.

>> 2. Headlines greater than n when H:n (e.g., level three headlines
>> when H
>> is set to 2) are exported as description lists.
>> Is this the intended behavior?
> This is how Bastien designed it, and it is similar to the HTML way,
> turning these into lists.  It works fine if there is any text before
> the plain list bullets.

When I use a paragraph of text instead of plain list bullets, the
subsequent paragraph becomes the definition of the headline, which
becomes the list label. Is this correct?

> Do you have a better proposal?

I suppose I was expecting the headings to become itemized lists if
num:nil or enumerated lists if num:t. But I realize that's probably not
the most straightforward behavior. I think it's easier for me to use
bullet lists in the org source than to request a change. :)

>> Would it be possible to have the latex exporter ignore markup
>> designated as html?
> I am unable to reproduce this, works fine for me.

You are right. I cannot reproduce this. I'm afraid it may have been due
to a typo. Sorry for the false alarm.

> OK, we have now #+begin_center

Again, thanks so much! This works beautifully and I've already used it
in a syllabus.

>> A related thought (and sorry for the very long email), is there any
>> way
>> to define these types of macros globally, rather than in-buffer? It
>> would be really nice to be able to set commonly used macros globally.
>> Even nicer would be the ability to define macros that are context
>> sensitive: i.e., one substitution for for LaTeX export, another
>> substitution for HTML export. This might make it easier to export the
>> same source file to different outputs. Just a wishlist item....
> Yes,  guess we could have global macros, and also macros that expand
> depending on exporter type.  I have not though much about it, maybe
> you'd like to draw up a syntax?

Thanks for considering this. I'll do some brainstorming and get back to you.


  reply	other threads:[~2009-03-18 16:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 19:16 Latex export bugs and a request Matthew Lundin
2009-03-16 21:16 ` Carsten Dominik
2009-03-18 16:33   ` Matthew Lundin [this message]
2009-03-19 10:04     ` Carsten Dominik
2009-03-20  2:43       ` Matthew Lundin
2009-03-21 17:21         ` Carsten Dominik
2009-03-21 20:32           ` Matthew Lundin
2009-03-22  7:03             ` Carsten Dominik
2009-03-21 18:32         ` Matthew Lundin

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=87bpryeqpm.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=dominik@science.uva.nl \
    --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).