From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: #+CATEGORY line being archived
Date: Mon, 19 Mar 2007 00:42:11 +0100 [thread overview]
Message-ID: <87fy82ce5o.fsf@bzg.ath.cx> (raw)
In-Reply-To: <c5beaf1d83b17bb47aa88f08c6266efc@science.uva.nl> (Carsten Dominik's message of "Sun\, 18 Mar 2007 21\:00\:53 +0100")
Carsten Dominik <dominik@science.uva.nl> writes:
> 1. Bastiens proposal, i.e. placing the parameter lines after the
> top-level heading. This works as long as the top-level heading itself
> is never pointed to by an agenda entry (the category would be wrong)
> and as long as you neve atempt to archive the top-level heading
> itself.
This is exactly what i do. I have several projects and i list them
within a single file :
,----
| #+CATEGORY: main_categeory
| #+ARCHIVE: main_archive::*
|
| * Project 1
| #+CATEGORY: project_1
| #+ARCHIVE: project1_archive::*
|
| ** task 1
|
| * Project 2
| #+CATEGORY: project_2
| #+ARCHIVE: project2_archive::*
|
| * Project 1
| #+CATEGORY: project_2
| #+ARCHIVE: project2_archive::*
`----
Archiving "** task 1" puts it in `project1_archive', as expected.
Archiving "* Project 1" will put it in `main_archive'.
For me "* Project 1" is not part of the project1-related tasks -- not
more than the filename of my main org file is part of this file. So the
headline "* Project 1" has not to be archived in `project1_archive', but
in `main_archive'. Hence the normal behavior suits my use very well.
Regards,
--
Bastien
next prev parent reply other threads:[~2007-03-18 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 14:21 #+CATEGORY line being archived Leo
2007-03-18 16:09 ` Bastien
2007-03-18 16:44 ` Leo
2007-03-18 20:00 ` Carsten Dominik
2007-03-18 20:16 ` Leo
2007-03-18 23:42 ` Bastien [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-20 19:18 Jost Burkardt
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=87fy82ce5o.fsf@bzg.ath.cx \
--to=bzg@altern.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).