emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ox-koma bug in subtree export
Date: Wed, 15 Jul 2015 23:13:17 +0200	[thread overview]
Message-ID: <20150715211317.GO18343@chitra.no-ip.org> (raw)
In-Reply-To: <87y4ihk5ho.fsf@gmx.us>

On Wed, Jul 15, 2015 at 01:46:59PM +0200, Rasmus wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > I'm using subtree export to write letters using ox-koma.  Everything
> > works except, all the closing statements from different subtrees get
> > accumulated when I export one of the subtrees.
> >
> > So with the attached Org file, when I export either of the subtrees, I
> > get a closing line like this: \closing{Regards, Kind Regards,}.
> 
> For your purpose you can add an :export_closing: property to your
> top-level heading.
> 
> * letter 1
>   :PROPERTIES:
>   :export_subject: Some subject
>   :export_closing: Regards,
>   :END:

Great, this works very well.

> > This used to work before.  That said, I never found it quite consistent
> > when using `#+closing:'.  I would have thought one should use a headline
> > like: to, enclosed, etc.
> 
> Maybe:
> 
>    * Regards,    :closing:
>      Signature

Something like that would be a lot more logical indeed.

> > Is this a bug?
> 
> From you example, I'd say 'no'.  Keywords are shared.  E.g. if you have
> 
>      #+latex_header: my important package
> 
> You'd want it to be loaded even when using a subtree.
> [OTOH, #+title is changed in subtree export....]

Hmm, makes sense.  I wonder how it was working though.

Thanks a lot.

-- 
Suvayu

Open source is the future. It sets us free.

next prev parent reply	other threads:[~2015-07-15 21:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 11:20 ox-koma bug in subtree export Suvayu Ali
2015-07-15 11:28 ` Suvayu Ali
2015-07-15 11:46 ` Rasmus
2015-07-15 21:13   ` Suvayu Ali [this message]
2015-07-15 22:47     ` Rasmus
2015-07-16  8:54       ` Suvayu Ali
2015-07-16  9:40         ` Rasmus
2015-07-16 10:25           ` Suvayu Ali
2015-07-16 10:44             ` Rasmus
2015-07-16 14:57               ` Suvayu Ali
2015-07-16 20:20                 ` Rasmus
2015-07-17  7:31                   ` Suvayu Ali

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=20150715211317.GO18343@chitra.no-ip.org \
    --to=fatkasuvayu+linux@gmail.com \
    --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

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).