From: Myles English <mylesenglish@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-koma-letter.el: Add support for 'location' koma variable
Date: Fri, 29 Jan 2016 22:08:10 +0000 [thread overview]
Message-ID: <878u38ghth.fsf@gmail.com> (raw)
In-Reply-To: <87bn84a8e4.fsf@gmx.us>
Rasmus,
Rasmus writes:
> I’m arguing for a solution that supports BOTH "one-off" and permanent
> data.
OK, sorry, I thought you were arguing for a heading tagged :location:
and against an option #+LOCATION or property :EXPORT_LOCATION:. How
about applying my patch please and the tagged heading can be developed
by someone™ 'later'.
> The keyword is convenient when you want to insert a pointer to field. I
>
> But for a one-off letter where I might need to include "one-off" details
> on the left, I’d rather type:
>
> * bank details :location:
> Acc. No.: 1234567890
> at Big Bank
> Sort Code: 11-22-33
>
> Than
>
> #+latex_header: \setkomavar{frombank}{\raggedright Acc.~No.:\,1234567890\\at Big Bank\\Sort Code: 11-22-33}
> #+Location: \usekomavar{frombank}
>
> To me the former reads much easier and hides away the technical details.
> Thus, I wish to see to see support for entry forms.
Alright, I get the general idea but in that specific case this would be
simpler:
#+LOCATION: \raggedright Acc.~No.:\,1234567890\\at Big Bank\\Sort Code: 11-22-33
Myles
next prev parent reply other threads:[~2016-01-29 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:32 [PATCH] ox-koma-letter.el: Add support for 'location' koma variable Myles English
2016-01-27 22:05 ` Rasmus
2016-01-28 11:19 ` Myles English
2016-01-28 12:20 ` Rasmus
2016-01-28 22:00 ` Myles English
2016-01-29 12:16 ` Rasmus
2016-01-29 22:08 ` Myles English [this message]
2016-01-29 22:39 ` Rasmus
2016-02-15 13:51 ` Myles English
2016-02-17 22:53 ` Rasmus
2016-03-31 19:56 ` Rasmus Pank Roulund
2016-03-31 23:32 ` Myles English
2016-04-03 11:33 ` Rasmus
2016-04-04 0:54 ` Myles English
2016-04-07 8:09 ` Rasmus
2016-01-28 20:17 ` Eric S Fraga
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=878u38ghth.fsf@gmail.com \
--to=mylesenglish@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).