Hi Myles,
Myles English <mylesengl...@gmail.com> writes:
>> But is it much neater than:
>>
>> ** bank details :location:
>> Acc. no.: 12345
>> Big Bank Corp
>> Sort code: 1122
>
> Err, yes it is? And anyway, that data is in my LCO file, I don't want
> to duplicate it.
That's fine, but one might want to put information there that's specific
to a particular letter (and thus no LCO file is readily available or is an
additional level of complexity).
>> For temporary data, I’d rather have it like in my example. For permanent
>> data I can keep it in a .lco file.
>
> Yes, that is what I have done (hmmm, I am beginning to sense a
> fundamental misunderstanding here). My bank account details are
> permanent data and are in a LCO file.
I’m arguing for a solution that supports BOTH "one-off" and permanent
data.
> #+BEGIN_QUOTE
> ...I would still prefer this way for the simple case of
> inserting bank details:
>
> ______________________
>
> ** Change of address
> :EXPORT_LOCATION: \usekomavar{frombank}
>
> I have moved.
> ______________________
>
> Where the frombank variable has been set in the LCO file:
>
> \setkomavar{frombank}{\raggedright Acc.~No.:\,1234567890\\at Big
> Bank\\Sort Code: 11-22-33}
>
> The bank details only appear in a letter when the property is set.
> #+END_QUOTE
>
> That property mentioned is the :EXPORT_LOCATION: property. You can set
> it to whatever you like, referencing something in your LCO file or
> temporary data.
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.
Rasmus
--
The Kids call him Billy the Saint
