From: Matthew Lundin <mdl@imapmail.org>
To: Matthew Lundin <mdl@imapmail.org>
Cc: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: Latex export bugs and a request
Date: Sat, 21 Mar 2009 13:32:22 -0500 [thread overview]
Message-ID: <m2eiwqvia1.fsf@fastmail.fm> (raw)
In-Reply-To: <m2r60skj70.fsf@fastmail.fm> (Matthew Lundin's message of "Thu\, 19 Mar 2009 21\:43\:31 -0500")
Matthew Lundin <mdl@imapmail.org> writes:
> Hi Carsten,
>
>>>>> 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?
>>
>> I am confused, could you make a detailed example, please?
I'm a bit chagrined to admit that there is already a variable that does
what I want. So sorry for the false alarm. I set the variable
org-export-latex-low-levels to a string--\subparagraph{%s}--and then
redefined the formatting of the subparagraph macro in the article
preamble org-export-latex-classes. So everything is fine.
I suppose it would be nice to add an itemize possibility to the variable
org-export-latex-low-levels, but by no means urgent. This is a wishlist
item and nothing more....
Thanks,
Matt
prev parent reply other threads:[~2009-03-21 18:32 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
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 [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=m2eiwqvia1.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--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).