emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: How to export casual letter without from and to address?
Date: Sun, 06 Mar 2016 20:02:59 +0100	[thread overview]
Message-ID: <871t7nig4c.fsf@gmx.us> (raw)
In-Reply-To: 87twkkzori.fsf@mbork.pl

Marcin Borkowski <mbork@mbork.pl> writes:

> On 2016-03-05, at 19:56, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
>> On Saturday,  5 Mar 2016 at 10:47, York Zhao wrote:
>>>> Why use a letter exporter (koma?) if you don't want something that looks like
>>>> a letter?
>>>
>>> I wanted it to be a letter in all aspects, except that it doesn't have the "from
>>> address" and "to address" in the header. More specifically, I want my letter
>>> looks like:
>>>
>>>   Hi Flora,
>>>
>>>   Blah blah blah!
>>>
>>>   Regards,
>>>
>>>   York
>>>
>>>> simply write it as a normal org document and export it to pdf or odt or
>>>> whatever you wish to send.
>>>
>>> The problem is, it seems to me that to export to pdf, LaTeX export is the only
>>> way to go. But then you would have to choose a document class. Obviously you
>>> can't use "article", nor "book". So my question may probably rephrase as: which
>>> latex document class do you use to export the letter "as is"?
>>
>> Ah, okay, I see. Well, you could try something along the lines of:
>>
>> #+begin_src org
>>   ,#+title:
>>   ,#+author:
>>   ,#+date:
>>   ,#+options: toc:nil num:nil
>>   ,*
>>   Hi Flora
>>
>>   Blah blah blah!
>>
>>   Regards,
>>
>>   # leave some room for signature
>>   \vspace*{1.5cm}
>>
>>   York
>> #+end_src
>>
>> where the headline has a space after the "*".  You might want to play
>> with parindent and parskip LaTeX variables if you don't like the
>> default.
>>
>> Alternatively, there may be other LaTeX styles that could give you what
>> you want with a little customisation although probably unlikely.  For
>> instance, have a look at http://www.latextemplates.com/ and maybe create
>> your own using the custom class example?
>
> You could also stick something like
>
> \let\maketitle=\relax

This only works in latex.  A backend-agnostic solution could be:

     #+options: title:nil

Though maybe it's undesirable in some other aspect.

Rasmus

-- 
May the Force be with you

  reply	other threads:[~2016-03-06 19:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  5:12 How to export casual letter without from and to address? York Zhao
2016-03-05  3:36 ` York Zhao
2016-03-05 10:12   ` Eric S Fraga
2016-03-05 11:22     ` H. Dieter Wilhelm
2016-03-05 15:57       ` York Zhao
2016-03-06 10:38         ` H. Dieter Wilhelm
2016-03-05 15:47     ` York Zhao
2016-03-05 17:33       ` Marcin Borkowski
2016-03-05 18:56       ` Eric S Fraga
2016-03-05 19:52         ` Marcin Borkowski
2016-03-06 19:02           ` Rasmus [this message]
2016-03-06  3:15       ` Nick Dokos
2016-03-06 19:04 ` Rasmus
2016-03-07  1:11   ` York Zhao
2016-03-24 12:32 ` rbenit68

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=871t7nig4c.fsf@gmx.us \
    --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).