From: AW <alexander.willand@t-online.de>
To: emacs-orgmode@gnu.org, ian@manor-farm.org
Subject: Re: Org/LaTex setup for Business Letter Revisited
Date: Thu, 27 Dec 2012 08:31:51 +0100 [thread overview]
Message-ID: <3902057.9vSfNFHHgc@linux-ik7b.site> (raw)
In-Reply-To: <50D82370.5040308@wilkesley.net>
Am Montag, 24. Dezember 2012, 09:42:08 schrieb Ian Barton:
> I have been following the various threads about using the scrlttr2
> class. However, none of them quite worked for me.
>
> I have come up with the following hack using Babel. There are three
> files attached which illustrates the general principles.
Ian, this is really of interest to me, but I don't quite get it.
>
> * koma variables which don't change are defined in an LCO file.
So this is the usual LCO file, in a place where kpathsea will find it, namely at
~/texmf/tex/latex/ -- right?
> * koma variables (toaddress, etc) which change between letters are
> defined using org PROPERTIES.
> * a letter template in defined in a latex src block.
But what is the sense of having a LaTeX scr block? I'd like to outsource this
somewhere as a template. Or is it necessary in each file including a letter?
> * The letter body is written in an org_mode src block.
> * The final letter is produced by tangling the body, the lco file and
> the letter template.
"tangling" -- could you elaborate, please?
>
> In normal use you would simply modify the PROPERTIES and body text to
> suit each letter. The whole thing can probably be made into a yasnippet.
>
"the whole thing"? What has to be included in the snippet?
> Suggestions for improvement welcome, as the existing stuff is just a
> quick hack.
>
> Happy Christmas everyone and best wishes for the New Year.
Yeah, and thanks to you for your time and effort,
Alexander
>
> Ian.
prev parent reply other threads:[~2012-12-27 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 9:42 Org/LaTex setup for Business Letter Revisited Ian Barton
2012-12-27 7:31 ` AW [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=3902057.9vSfNFHHgc@linux-ik7b.site \
--to=alexander.willand@t-online.de \
--cc=emacs-orgmode@gnu.org \
--cc=ian@manor-farm.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).