emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [bug] ox-org.el subtree export appears broken
Date: Wed, 06 Nov 2013 14:21:54 -0700	[thread overview]
Message-ID: <87bo1x9qfh.fsf@gmail.com> (raw)
In-Reply-To: <8761s5bcr3.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 06 Nov 2013 19:34:24 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> Specifically, the title is not taken from the current heading, and
>> subheadings are not promoted to the top level.
>
> I partly fixed this: subheadings should now get correct level.
>

Confirmed, thanks.

>
> OTOH, "ox-org" back-end doesn't insert any keyword (DATE, AUTHOR,
> TITLE), subtree export or not. If we add such keywords during subtree
> export, we also have to add them during regular export. I'm not
> convinced this is within the scope of that back-end.
>
> What do you think?
>

I don't know as much about backends so I'm willing to defer.

My initial thoughts are that inserting keywords *with* values while not
inserting empty keywords would be the most intuitive.  This way a
subtree export would insert a title (taken from the subtree heading),
and any other keywords set as subtree properties, but whole-buffer
export wouldn't insert any keywords which weren't present in the
original.

I hope this makes sense, and thanks for the quick fix.

Best,

>
>
> Regards,

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

  reply	other threads:[~2013-11-06 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 17:59 [bug] ox-org.el subtree export appears broken Eric Schulte
2013-11-06 18:34 ` Nicolas Goaziou
2013-11-06 21:21   ` Eric Schulte [this message]
2013-11-06 22:02     ` Nicolas Goaziou
2013-11-11  2:12       ` Eric Schulte
2013-11-15 23:25         ` Nicolas Goaziou

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=87bo1x9qfh.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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).