From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [PATCH] ox-koma-letter.el: Add support for 'location' koma variable Date: Fri, 29 Jan 2016 13:16:03 +0100 Message-ID: <87bn84a8e4.fsf@gmx.us> References: <87egd2ho08.fsf@gmail.com> <87vb6eekzj.fsf@gmx.us> <87d1smgdcw.fsf@gmail.com> <87k2mtdhem.fsf@gmx.us> <87a8npgy92.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50022) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aP7zF-00029v-4I for emacs-orgmode@gnu.org; Fri, 29 Jan 2016 07:17:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aP7zB-0002mk-RR for emacs-orgmode@gnu.org; Fri, 29 Jan 2016 07:17:13 -0500 Received: from plane.gmane.org ([80.91.229.3]:38671) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aP7zB-0002mc-K0 for emacs-orgmode@gnu.org; Fri, 29 Jan 2016 07:17:09 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aP7yl-0002ir-S8 for emacs-orgmode@gnu.org; Fri, 29 Jan 2016 13:16:44 +0100 Received: from 62.80.108.15 ([62.80.108.15]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Jan 2016 13:16:43 +0100 Received: from rasmus by 62.80.108.15 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Jan 2016 13:16:43 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Myles, Myles English 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