From: Matthew Lundin <email@example.com>
To: Matthew Lundin <firstname.lastname@example.org>
Subject: Re: Problem with archive location
Date: Sun, 11 Jan 2009 09:28:23 -0600 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Matthew Lundin's message of "Sun\, 11 Jan 2009 09\:08\:56 -0600")
I should clarify a couple things in the previous post:
Matthew Lundin <email@example.com> writes:
> I had one more question/request concerning archives.
I'm specifically referring to org-archive-location here.
> Would it perhaps be possible to enable the file name substitution
> (i.e., "%s") after the double semi-colon, so that the file name can
> be used as a headline within the archive file?
This should read "after the double colon".
next prev parent reply other threads:[~2009-01-11 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 17:55 Problem with archive location Matthew Lundin
2009-01-10 20:57 ` Carsten Dominik
2009-01-11 15:08 ` Matthew Lundin
2009-01-11 15:28 ` Matthew Lundin [this message]
2009-01-11 16:47 ` Matthew Lundin
2009-01-13 7:40 ` Carsten Dominik
2009-01-13 11:47 ` Matthew Lundin
2009-01-17 7:58 ` Carsten Dominik
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).