emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Eliachevitch <m.eliachevitch@posteo.de>
To: William Denton <wtd@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: LaTeX letters in Org
Date: Fri, 18 Feb 2022 11:43:56 +0000	[thread overview]
Message-ID: <87a6eocqi0.fsf@posteo.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2201291225520.68511@shell3.miskatonic.org>

Hi Bill,

On 2022-01-29 at 12:39 -05, William Denton <wtd@pobox.com> wrote:

> I wrote up how to use Org to write letters with the LaTeX letter class. Here's
> the link in case anyone's interested:
> https://www.miskatonic.org/2022/01/28/latex-letters-in-org/

Cool, I'll try to remember this for when I write my next letter. You write

> I found it safest to use the #+latex: way of including LaTeX fragments. It doesn’t mess up the syntax highlight or the exporting.

When I have multiple lines of latex, I prefer including a latex export block over multiple `#+latex` lines, e.g.

    #+begin_export latex
    \ps{P.S.  I need not tell you this is a secret.  Good-night again.}

If you have `org-src-fontify-natively' to `t', this will even get you latex-syntax highlighting within the block, or if you find that too distracting, you can set that variable to `nil'. Sometimes it's useful to edit the latex-block in your latex major mode via `org-edit-export-block' (<C-c '>).

Currently the number of org export options you need is not too high, but if it grows you can move boilerplate of the letter itself via either `#+setupfile:` or just including a separate latex file. I'm think if there's a way to adapt the latex class

For not using the title, via not set `#+options: title:nil' ?

For this kind of short writing I'm always wondering whether doing it in org-mode is really worth it. I see a trade-of between the convenience of  org-markup (e.g. emphasis markers, itemize lists, links, …), and the inconvience of adding literal latex to org-mode, which is just a bit more cumbersome than doing so in an actual latex file with a latex major mode*. Especiall since you don't use headers anyway. If I do some writing where the transition between notes to the final product is fluid, then it's a no-brainer and I would do so from org immediately. But because I just enjoy writing in org-mode so much more, I would probably also do it like you from now on.

* I can use auctex in latex export blocks, but I don't think latex language servers like digestif (https://github.com/astoff/digestif) work well with them.


Michael Eliachevitch
Public PGP Key: https://keyoxide.org/hkp/546908c782383ad0e7d894ec1b8f95c8125dce31

  reply	other threads:[~2022-02-18 12:24 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 [this message]
2022-02-18 15:14   ` Dr. Arne Babenhauserheide
2022-02-18 16:55     ` Michael Eliachevitch
2022-02-18 18:59       ` Alan E. Davis
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=87a6eocqi0.fsf@posteo.de \
    --to=m.eliachevitch@posteo.de \
    --cc=emacs-orgmode@gnu.org \
    --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).