From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [patch] ox-koma-letter
Date: Sat, 02 Mar 2013 18:53:48 +0100 [thread overview]
Message-ID: <87haktpu1f.fsf@pank.eu> (raw)
In-Reply-To: <20130228151912.GZ24632@strey.biz> (Michael Strey's message of "Thu, 28 Feb 2013 16:19:12 +0100")
Michael Strey <mstrey@strey.biz> writes:> Rasmus,
>> In fact to use the scrlttr2 support in Org I had to adjust a LCO files
>> because it's currently loaded after LATEX_HEADER arguments (so all
>> customization was overwritten). I didn't like that.
>
> After this remark I checked my changes and compared them with the
> default code and behaviour of ox-koma-letter with the result that I
> reverted all of my deletions. The mentioned feature provides just the right
> hierarchy for my use case.
>
> - LCO overrides everything
> - options in the file override options in customization
> - options in customization override defaults in ox-koma-letter
>
> Nevertheless I agree that the "nil check" solution would allow more
> flexibility.
Cool, I'll look at it when time permits (which will not be next
week).
>> > Maybe we should write a user guide *before* further implementation
>> > steps.
>>
>> I agree. A "question zero" is whether we eventually want to have an
>> org-letter which could, in principle, output to something different
>> than scrlttr2.
>
> IMO one *good* solution for writing letters is enough. scrlttr2 is
> perfect for me and covers at least European conventions about how
> letters should look like. I don't know which LaTeX classes people from
> other parts of the globe prefer.
>
> At least we should try to make the user interface (the list of
> variables) universal enough to cover other classes as well.
I agree on semi-universal arguments and retaining the current
specialization to scrlttr2.
--
m-mm-mmm-mmmm bacon!
next prev parent reply other threads:[~2013-03-02 17:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 20:25 [patch] ox-koma-letter Rasmus
2013-02-26 9:50 ` Bastien
2013-02-26 11:53 ` Rasmus
2013-02-26 12:38 ` Michael Strey
2013-02-26 21:14 ` Rasmus
2013-02-27 10:51 ` Michael Strey
2013-02-27 12:13 ` Rasmus
2013-02-27 13:41 ` Sebastien Vauban
2013-02-27 16:48 ` Rasmus
2013-02-28 15:19 ` Michael Strey
2013-03-02 17:53 ` Rasmus [this message]
2013-03-01 13:17 ` Alan Schmitt
2013-03-02 10:26 ` Bastien
2013-03-02 15:50 ` Alan Schmitt
2013-03-02 18:12 ` Bastien
2013-03-02 17:54 ` Rasmus
2013-03-02 17:57 ` Rasmus
2013-03-02 19:21 ` Alan Schmitt
2013-03-02 21:58 ` Rasmus
2013-03-03 16:00 ` Alan Schmitt
2013-03-03 17:25 ` Nicolas Goaziou
2013-03-04 7:19 ` Alan Schmitt
2013-03-04 8:33 ` Nicolas Goaziou
2013-03-04 8:56 ` Alan Schmitt
2013-03-04 10:38 ` Rasmus
2013-03-04 20:38 ` Nicolas Goaziou
2013-03-05 9:08 ` Alan Schmitt
2013-03-05 9:52 ` Nicolas Goaziou
2013-03-05 10:51 ` Michael Strey
2013-03-05 12:23 ` Rasmus
2013-03-05 13:09 ` Michael Strey
2013-03-06 9:03 ` Alan Schmitt
2013-03-06 9:09 ` Nicolas Goaziou
2013-03-04 10:46 ` Michael Strey
2013-03-04 13:48 ` Alan Schmitt
2013-03-04 21:20 ` Rasmus
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=87haktpu1f.fsf@pank.eu \
--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).