From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: Bastien <bzg@gnu.org>,
emacs-orgmode@gnu.org, Luis Anaya <papoanaya@hotmail.com>
Subject: Re: Extending org-koma-letter.el
Date: Thu, 22 Nov 2012 17:40:41 +0100 [thread overview]
Message-ID: <87d2z5d20m.fsf@gmail.com> (raw)
In-Reply-To: <m2haohaaei.fsf@top-wifi.irisa.fr> (Alan Schmitt's message of "Thu, 22 Nov 2012 17:07:49 +0100")
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> I had to write yet another letter, so I digged into this and it's now
> working well enough for me. I made a few changes to the file (which I
> attach):
>
> - fixed bugs to the menu (export to pdf, open pdf), added "export to tex
> file"
> - put a default address "no address" instead of a blank line, otherwise
> compilation fails
> - moved the lco file input before the preamble, so that one can specify
> some additional information (like packages). (This may be
> questionable, don't hesitate to let me know.)
I think that's fine.
> I now have two questions: a technical one and a non-technical one.
>
> The technical one: I see that org-e-koma extends the latex exporter with
> some options:
>
> (org-export-define-derived-backend koma-letter e-latex
> :options-alist
> ((:closing "CLOSING" nil org-koma-letter-closing)
> (:from-address "FROM_ADDRESS" nil org-koma-letter-from-address newline)
> ...
>
> These options have 3 arguments instead of 4 in the definition of options
> in org-e-latex:
>
> :options-alist ((:date "DATE" nil org-e-latex-date-format t)
> (:latex-class "LATEX_CLASS" nil org-e-latex-default-class t)
> ...
>
> Is the missing argument the one that lets EXPORT_OPTIONS specify if some
> parts can be omitted for subtree export? Or is it something different?
It's something different: the last argument defines the behaviour when
more than one keyword is found in the buffer. When unspecified, it
defaults to nil. The syntax is the same as `org-export-options-alist',
which defines back-end agnostic export options. You should have a look
at its docstring.
> The non-technical question: I understand this exporter is just a proof
> of concept, but it is working quite well for me, and I'm ready to help
> tweaking this. If I do further modifications, should I send them to the
> list?
I classified it as "proof of concept" because I was too lazy to dig into
Scrlttr2 documentation and provide a complete enough letter back-end.
I would be glad that someone maintains it.
I think the simplest solution is to:
1. Ask for push access to Org.
2. Commit file in contrib/ directory.
3. Add yourself as Maintainer in it (or Author, for that matter).
4. Commit additional changes when you see fit, without sending the
file over and over to the ML.
For point 1, see http://orgmode.org/worg/org-contribute.html (For Org
Developers)
Also, it would be nice if you signed FSF papers.
Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-11-22 16:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 12:49 Org/LaTeX set-up for business letters? Thorsten Jolitz
2012-07-05 13:12 ` suvayu ali
2012-07-05 19:00 ` Thorsten Jolitz
2012-07-05 22:00 ` suvayu ali
2012-07-05 22:47 ` Thorsten Jolitz
2012-07-06 8:47 ` Michael Strey
2012-07-06 16:35 ` Thorsten Jolitz
2012-07-06 18:11 ` suvayu ali
2012-07-06 19:11 ` Thorsten Jolitz
2012-07-06 19:23 ` Bastien
2012-07-06 19:44 ` Nicolas Goaziou
2012-07-07 2:42 ` Mehul Sanghvi
2012-07-07 11:48 ` Thorsten Jolitz
2012-07-07 1:55 ` Vikas Rawal
2012-07-07 11:58 ` Thorsten Jolitz
2012-07-08 10:34 ` Sebastien Vauban
2012-07-06 19:08 ` HowTo: Letter template method using yasnippet (was: Org/LaTeX set-up for business letters?) Karl Voit
2012-07-06 22:35 ` HowTo: Letter template method using yasnippet Nicolas Goaziou
2012-07-07 0:34 ` Thorsten Jolitz
2012-07-07 9:35 ` Karl Voit
2012-07-08 9:08 ` AW
2012-07-08 13:34 ` Nicolas Goaziou
2012-07-08 14:57 ` AW
2012-07-27 16:24 ` Extending org-koma-letter.el (was: HowTo: Letter template method using yasnippet) Rasmus
2012-07-29 18:31 ` Extending org-koma-letter.el Nicolas Goaziou
2012-07-31 10:14 ` Luis Anaya
2012-08-03 8:19 ` Nicolas Goaziou
2012-08-03 14:23 ` Luis Anaya
2012-08-03 16:24 ` Bastien
2012-08-04 0:40 ` Luis Anaya
2012-11-06 15:31 ` Alan Schmitt
2012-11-13 22:56 ` Nicolas Goaziou
2012-11-14 16:48 ` Alan Schmitt
2012-11-20 3:14 ` Luis Anaya
2012-11-22 16:07 ` Alan Schmitt
2012-11-22 16:32 ` Rasmus
2012-11-22 16:40 ` Nicolas Goaziou [this message]
2012-11-23 8:34 ` Alan Schmitt
2012-11-23 11:51 ` Nicolas Goaziou
2012-11-26 8:01 ` Alan Schmitt
2012-11-26 12:48 ` Bastien
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=87d2z5d20m.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=alan.schmitt@polytechnique.org \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=papoanaya@hotmail.com \
/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).