From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: #+CATEGORY line being archived Date: Sun, 18 Mar 2007 21:00:53 +0100 Message-ID: References: <87fy82v8hf.fsf@bzg.ath.cx> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HT1aG-0007Cn-NH for emacs-orgmode@gnu.org; Sun, 18 Mar 2007 16:02:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HT1aF-0007Cb-96 for emacs-orgmode@gnu.org; Sun, 18 Mar 2007 16:02:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HT1aF-0007CY-3a for emacs-orgmode@gnu.org; Sun, 18 Mar 2007 15:02:27 -0500 Received: from korteweg.uva.nl ([146.50.98.70]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HT1Yr-0001hk-GR for emacs-orgmode@gnu.org; Sun, 18 Mar 2007 16:01:01 -0400 In-Reply-To: <87fy82v8hf.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org On Mar 18, 2007, at 17:09, Bastien wrote: > Leo 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