From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: koma letter exporter: changing the priority of options
Date: Fri, 19 Jul 2013 15:01:57 +0200 [thread overview]
Message-ID: <m238rawvne.fsf@polytechnique.org> (raw)
In-Reply-To: <874nd6we8q.fsf@pank.eu>
Hello,
rasmus@gmx.us writes:
> Viktor Rosenfeld <listuser36@gmail.com> writes:
>
>>> ,----
>>> | \KOMAoption{backaddress}{true}
>>> | \KOMAoption{foldmarks}{true}
>>> | \KOMAoption{fromphone}{true}
>>> | \KOMAoption{fromemail}{true}
>>> `----
>>
>> Perhaps the best option would be to change the default value of these
>> variables to nil? We have almost every option that personalizes
>> a letter, e.g., opening and closing, set to nil already. The only
>> benefit of having default values is to show off the features of
>> org-koma-letter. But it seems to be interfering with people's workflow
>> so best turn them off.
>
> Doesn't this also more or less correspond to the default value of
> scrlttr2? If so there's no reason to add it to the tex file and nil
> is indeed a better default.
It took me a while to look at this (basically until I had to write
another letter), but here is a patch I propose to commit to do this.
--8<---------------cut here---------------start------------->8---
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 44626a9..8a98689 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -228,7 +228,7 @@ English manual of 2012-07-22)"
-(defcustom org-koma-letter-use-backaddress t
+(defcustom org-koma-letter-use-backaddress nil
"Print return address in small line above to address."
:group 'org-export-koma-letter
:type 'boolean)
@@ -243,12 +243,12 @@ Use `foldmarks:true' to activate default fold marks or
:group 'org-export-koma-letter
:type 'string)
-(defcustom org-koma-letter-use-phone t
+(defcustom org-koma-letter-use-phone nil
"Print sender's phone number."
:group 'org-export-koma-letter
:type 'boolean)
-(defcustom org-koma-letter-use-email t
+(defcustom org-koma-letter-use-email nil
"Print sender's email address."
:group 'org-export-koma-letter
:type 'boolean)
@@ -554,10 +554,10 @@ holding export options."
(with-phone (plist-get info :with-phone))
(with-email (plist-get info :with-email)))
(concat
- (format "\\KOMAoption{backaddress}{%s}\n" (if with-backaddress "true" "false"))
- (format "\\KOMAoption{foldmarks}{%s}\n" (if with-foldmarks with-foldmarks "false"))
- (format "\\KOMAoption{fromphone}{%s}\n" (if with-phone "true" "false"))
- (format "\\KOMAoption{fromemail}{%s}\n" (if with-email "true" "false"))))
+ (if with-backaddress (format "\\KOMAoption{backaddress}{true}\n") "")
+ (if (not (equal with-foldmarks "true")) (format "\\KOMAoption{foldmarks}{%s}\n" with-foldmarks) "")
+ (if with-phone (format "\\KOMAoption{fromphone}{true}\n") "")
+ (if with-email (format "\\KOMAoption{fromemail}{true}\n") "")))
;; Document start
"\\begin{document}\n\n"
;; Subject
--8<---------------cut here---------------end--------------->8---
I did some experiments and it seems that by default "foldmarks" is
true. The idea behind the patch is that, if we don't change the default
values, then things are not output. Let me know if this is fine with you
and I'll commit this. (I'll also edit the work with the new default
values.)
I still have an issue with the default value for email. I have set-up my
email address in emacs, and it's picked up by the koma exporter. I want
to use a different address in my work letters (which use a custom lco
file), but the email address is overridden by the one picked up by the
following function:
(defun org-koma-letter-email ()
"Return the current `user-mail-address'"
user-mail-address)
What I propose is the following:
- we leave the default AUTHOR and EMAIL at nil
- if they are still nil, we output the default values _before_ inputting
the lco file
- if they are no longer nil, we output their values _after_ inputting
the lco file
This way, if they are not defined in the file, then the lco can override
them, otherwise the local option will be the one used.
What do you think?
Alan
next prev parent reply other threads:[~2013-07-19 13:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 10:12 koma letter exporter: changing the priority of options Alan Schmitt
2013-06-09 18:00 ` Viktor Rosenfeld
2013-06-10 7:14 ` Alan Schmitt
2013-06-10 8:40 ` Rasmus
2013-07-19 13:01 ` Alan Schmitt [this message]
2013-07-19 18:57 ` Rasmus
2013-07-20 11:58 ` Viktor Rosenfeld
2013-07-20 12:59 ` Rasmus
2013-07-20 11:55 ` Viktor Rosenfeld
2013-07-22 7:14 ` Alan Schmitt
2013-07-22 7:50 ` Nicolas Goaziou
2013-07-22 12:42 ` Alan Schmitt
2013-07-22 13:17 ` Nicolas Goaziou
2013-07-22 13:45 ` Alan Schmitt
2013-07-22 14:53 ` Alan Schmitt
2013-08-17 16:37 ` Rasmus
2013-08-17 18:16 ` Rasmus
2013-08-27 8:02 ` Alan Schmitt
2013-08-27 8:29 ` Alan Schmitt
2013-08-31 14:35 ` Alan Schmitt
2013-08-31 16:05 ` Rasmus
2013-08-28 11:26 ` Rasmus
2013-08-28 11:43 ` Alan Schmitt
2013-08-28 12:06 ` Rasmus
2013-08-28 13:23 ` Alan Schmitt
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=m238rawvne.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--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).