From: Grant Rettke <gcr@wisdomandwonder.com>
To: Bastien <bzg@gnu.org>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Patch adding from-logo commentary ox-koma-letter.el
Date: Mon, 18 Jun 2018 12:27:31 -0500 [thread overview]
Message-ID: <CAAjq1mdUSWsNQWMjUii=Tt6s6zcRg=fwdAP5vHmHEuUZgq0kbg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
On Sat, Apr 28, 2018 at 1:32 AM, Bastien <bzg@gnu.org> wrote:
> Hi Grant,
>
> Grant Rettke <gcr@wisdomandwonder.com> writes:
>
>> Here is how it works, the same way as the other ones:
>
> If needed, don't hesitate to advertize this in the comment section
> of the code.
Here is a patch to a commentary on how to use FROM_LOGO.
[-- Attachment #2: 0001-exporters-koma-letter-export.org-Add-FROM_LOGO-comme.patch --]
[-- Type: application/octet-stream, Size: 1609 bytes --]
From 324fc4dc82d929cb9310d8f491b6613c421e6a6c Mon Sep 17 00:00:00 2001
From: Grant Rettke <gcr@wisdomandwonder.com>
Date: Mon, 18 Jun 2018 12:14:04 -0500
Subject: [PATCH] * exporters/koma-letter-export.org: Add FROM_LOGO commentary.
* koma-letter-export.org: Enhance commentary on FROM_LOGO
Using FROM_LOGO is noticeably different than using the other options because:
1. It requires providing an image file for the logo.
2. It requires providing LaTeX markup to specify that logo.
Although the function document ion mentions the markup to use, it
doesn't explain that the user needs to provide a logo file in the same
directory as the letter.
---
contrib/lisp/ox-koma-letter.el | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index fc6599fe7..4c09b456a 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -77,6 +77,12 @@
;; (See also `org-koma-letter-author'),
;; - EMAIL: Same as AUTHOR. (see also `org-koma-letter-email'),
;;
+;; Unlike using other variables, FROM_LOGO requires LaTeX markup and
+;; an image file for the logo. This is the markup to provide:
+;; \includegraphics{logo}. It's argument is the name of the logo file
+;; but without the file extension. The logo file needs to be located in
+;; the same directory as the letter that you are writing.
+;;
;; Headlines are in general ignored. However, headlines with special
;; tags can be used for specified contents like postscript (ps),
;; carbon copy (cc), enclosures (encl) and code to be inserted after
--
2.17.1
next reply other threads:[~2018-06-18 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 17:27 Grant Rettke [this message]
2018-06-19 8:11 ` Patch adding from-logo commentary ox-koma-letter.el Nicolas Goaziou
2018-06-20 22:38 ` Grant Rettke
2018-06-21 3:40 ` Van L
2018-06-21 9:37 ` Nicolas Goaziou
2018-06-24 1:32 ` Grant Rettke
2018-06-27 14:28 ` Nicolas Goaziou
2018-06-28 16:03 ` Grant Rettke
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='CAAjq1mdUSWsNQWMjUii=Tt6s6zcRg=fwdAP5vHmHEuUZgq0kbg@mail.gmail.com' \
--to=gcr@wisdomandwonder.com \
--cc=bzg@gnu.org \
--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).