From: Kyle Meyer <kyle@kyleam.com>
To: "Göktuğ Kayaalp" <self@gkayaalp.com>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Export datetree item subtree with its date, not the file's
Date: Sat, 17 Oct 2015 03:33:08 -0400 [thread overview]
Message-ID: <87mvvi9cgb.fsf@kyleam.com> (raw)
In-Reply-To: <87zj01a9d6.fsf@gkayaalp.com> ("Göktuğ Kayaalp"'s message of "Fri, 02 Oct 2015 12:49:09 +0300")
Hello,
self@gkayaalp.com (Göktuğ Kayaalp) writes:
> Hi,
>
> This is my first post to this group, so I'm sorry if I'm skipping any
> conventions.
Welcome to the list. Sorry for the lack of responses to your post.
It's a high traffic list, and sometimes posts fall through.
> My overall structure is like this:
[...]
> #+DATE:
> * 2015
> ** 2015-09 September
> *** 2015-09-16 Wednesday
> **** İtalyanca Dil Uygulamaları I :2015_2016:ITDE2016:
> [2015-09-16 Wed]
[...]
> When I export-subtree the bottommost entry, I want the date in the
> exported pdf to be 2015-09-16, not today, nor the date in "#+DATE:",
> which is deliberately empty to not let a wrong date to appear in the
> exported file.
>
> I tried setting a date property which didn't have an effect, and also
> adding a "#+DATE: [a date...]" under every lecture note entry heading,
> in which case the date of the last entry in the file got used, so if I
> exported the notes from 2015-09-16, and the last time I added a note was
> the 19th, the exported file had the date 2015-09-19.
Have you tried the EXPORT_DATE property? I believe it'd look something
like this
* 2015
** 2015-09 September
*** 2015-09-16 Wednesday
**** İtalyanca Dil Uygulamaları I :2015_2016:ITDE2016:
:PROPERTIES:
:EXPORT_DATE: 2015-09-16
:END:
which you could export using with export scope set to "subtree".
--
Kyle
next prev parent reply other threads:[~2015-10-17 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 9:49 Export datetree item subtree with its date, not the file's Göktuğ Kayaalp
2015-10-17 7:33 ` Kyle Meyer [this message]
2015-10-20 14:49 ` Göktuğ Kayaalp
2015-10-21 5:50 ` Kyle Meyer
2015-10-21 8:42 ` Eric S Fraga
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=87mvvi9cgb.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=self@gkayaalp.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).