emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: Michael Eliachevitch <m.eliachevitch@posteo.de>
Cc: William Denton <wtd@pobox.com>,
	"Dr. Arne Babenhauserheide" <arne_bab@web.de>,
	org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX letters in Org
Date: Fri, 18 Feb 2022 10:59:00 -0800	[thread overview]
Message-ID: <CAF-1L2RB8uFuTnoNZ7WQB0+OLcJEGugBX+P2cD56LoTDfmoseg@mail.gmail.com> (raw)
In-Reply-To: <87pmnkru12.fsf@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]

I had a set of three capture templates for memos, a number of years ago.
It was very convenient.  A letter is usually pretty much the same thing.  I
don't even know whether I have the original templates around anymore; it
should be pretty easy to implement.  IMHO, easier than dealing with all of
the header materials you are describing.  I think, anyway.

Two files were invoked: a header and a tail.  Then there were capture
template interactively filled addressee and whatever else.  One had a
letterhead.  It was, admittedly, a kludge.  A kludge that worked and saved
a lot of time.   For memos it's maybe more sensible, as they are quick
one-offs, for the most part.

Alan Davis

On Fri, Feb 18, 2022 at 9:03 AM Michael Eliachevitch <
m.eliachevitch@posteo.de> wrote:

> Hi Arne,
> > Alternatively add a capture-template that creates a letter. Then M-x
> > org-capture L (or such) would create a new letter prefilled with
> > everything you typically need.
> Thanks, weird I didn't think of it. Capture templates are awesome and
> powerful. Mostly I use them for some tasks, notes and journalling-type
> entries, not for long-form writing. But as a letters are usually short and
> writting in one session, capture-templates seem a good fit.
> Cheers, Michael
> --
> Michael Eliachevitch
> Public PGP Key:
> https://keyoxide.org/hkp/546908c782383ad0e7d894ec1b8f95c8125dce31

      "As we enjoy great advantages from the inventions of others, we *should
be glad of an opportunity to serve others* by any invention of ours, and
this we should do freely and generously."   ---Benjamin Franklin

      "This ignorance about the limits of the earth's ability to absorb
       pollutants should be reason enough for caution in the release
       of polluting substances."
                   ---Meadows et al.   1972.  Limits to Growth
(p. 81)

[-- Attachment #2: Type: text/html, Size: 3036 bytes --]

  reply	other threads:[~2022-02-18 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 17:39 LaTeX letters in Org William Denton
2022-02-18 11:43 ` Michael Eliachevitch
2022-02-18 15:14   ` Dr. Arne Babenhauserheide
2022-02-18 16:55     ` Michael Eliachevitch
2022-02-18 18:59       ` Alan E. Davis [this message]
2022-02-20 13:47 ` Christian Heinrich
2022-02-21 16:38   ` Michael Eliachevitch

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:

  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=CAF-1L2RB8uFuTnoNZ7WQB0+OLcJEGugBX+P2cD56LoTDfmoseg@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=m.eliachevitch@posteo.de \
    --cc=wtd@pobox.com \


* 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


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).