From: Leo <sdl.web@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: #+CATEGORY line being archived
Date: Sun, 18 Mar 2007 20:16:36 +0000 [thread overview]
Message-ID: <m2k5xeqpcr.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: c5beaf1d83b17bb47aa88f08c6266efc@science.uva.nl
On 2007-03-18, Carsten Dominik said:
> On Mar 18, 2007, at 17:09, Bastien wrote:
>
>> Leo <sdl.web@gmail.com> writes:
>>
>>> I found that if I do 'C-c C-x C-s' on headline "Done Task", all text
>>> up to the next headline "CR" is archived. This clearly is not the
>>> right behavior. Am I doing something wrong or is this a bug?
>>
>> I had this problem before and I'm now using #+ARCHIVE like this:
>>
>> ,----
>> | * Head1
>> | * Done Task
>> |
>> | * CR
>> | #+CATEGORY: CR
>> | #+ARCHIVE: %s_archive::* CR
>> | * anything
>> `----
>>
>
> This is a fundamental problem, for which there are only work-arounds,
> no solutions. Because of the structure of an outline, there is no such
> thing as a "location between sections". So just like Bastien describes,
> I also use work-arounds for this. Two come to mind.
>
> 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.
>
> 2. If (1) is not good enough, the only way I see is to insert a
> "parameter section", like this:
>
>
> ,----
> | * Head1
> | * Done Task
> |
> | * Params for the next file section
> | #+CATEGORY: CR
> | #+ARCHIVE: %s_archive::* CR
> |
> | * CR
> | * anything
> `----
>
> You could add an ARCHIVE tag to the parameter section, to keep it from
> opening.
>
> - Carsten
Thanks, Carsten. Bastien's seems simpler.
--
Leo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)
next prev parent reply other threads:[~2007-03-18 20:18 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 [this message]
2007-03-18 23:42 ` Bastien
-- 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=m2k5xeqpcr.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@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
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).