From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-koma-letter.el: Add support for section
Date: Mon, 04 Jan 2016 20:41:02 +0100 [thread overview]
Message-ID: <874mett9o1.fsf@gmx.us> (raw)
In-Reply-To: 87y4c5zzzzbpw5@me.localhost.invalid
Hi Daniele,
Daniele Pizzolli <dan@toel.it> writes:
> thanks for you comment. I try to explain my point of view better. Now
> the export to letter silently discard the headings text in the exported
> tex. This is quite bad, even if documented. As a user I want to change
> quite easily the export backend (text, latex, beamer, ...) while
> retaining most of my work. Every backend as it's own supported
> features, but discarding the input provided by the user does not provide
> the best user experience to me.
That's a fair point. Nonetheless,
> By the way this patch does not change the final output, if there is no
> section.lco available. So there should be no regression and only
> improvements.
> I really prefer something that instead of discarding the user input
> rewrite it to fit the backend features (if there is no heading/section
> support, use something like the start of paragraph, and support section
> only if enabled by the user) but this is beyond my coding abilities in
> elisp, so I sent the minimal working patch with the minimal impact on
> existing behaviour.
Whether sections.lco is available is nontrivial. As I remember the patch,
it also imposed level two headings to be sections.
If you really think this is the right approach, perhaps the "H:" option
could be used to set the special heading level... We’d need this since
you can specify the opening with a heading.
>>> +Add [sections] to LATEX_CLASS_OPTIONS with:
>>> +
>>> +#+LATEX_CLASS_OPTIONS: [sections]
>>> +
>>> +If section.lco is unavaliable the section are exported in the tex
>>> +source but not rendered in the final pdf.
>>
>> Whether section.lco is available or not is a complicated question. You
>> first need to figure out what is the tex distribution (what if it’s not in
>> PATH) and whether section.lco is available via something like kpsewhich.
>> Note that e.g. TL also looks in the current path.
>
> I use org to touch as less latex as possible, I just downloaded the
> section.lco and put in the same directory of my org file and everything
> was working. A little before I used apt-file search section.lco but
> since nothing was found I quickly reverted to the manual download. I
> wish that everything is packaged as distro package, but I can survive
> some manual work.
This is because sections.lco is not part of KOMA-Script (like titlepage¹).
E.g. on my system with TL:
$ kpsewhich sections.lco
/home/rasmus/.texmf/tex/latex/koma-script/sections.lco
kpsewhich/tex also looks in the current directory, which is why you can
just place it in the same folder.
Cheers,
Rasmus
Footnotes:
¹ http://www.komascript.de/titlepage
--
Warning: Everything saved will be lost
next prev parent reply other threads:[~2016-01-04 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 11:10 [PATCH] ox-koma-letter.el: Add support for section Daniele Pizzolli
2016-01-02 20:29 ` Rasmus
2016-01-04 10:27 ` Daniele Pizzolli
2016-01-04 19:41 ` Rasmus [this message]
2016-01-05 17:12 ` Daniele Pizzolli
2016-01-05 18:39 ` Rasmus
-- strict thread matches above, loose matches on Subject: below --
2016-01-02 11:10 Daniele Pizzolli
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=874mett9o1.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).