From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian van den Broek Subject: Re: possible misfeature regarding multiple #+ARCHIVE lines in a file Date: Sat, 01 Sep 2007 18:05:31 -0400 Message-ID: <46D9E22B.10207@cc.umanitoba.ca> References: <46D9DEE6.6060503@cc.umanitoba.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IRb5z-0005QC-DZ for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 18:05:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IRb5x-0005Q0-U4 for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 18:05:35 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IRb5x-0005Pq-PB for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 18:05:33 -0400 Received: from electra.cc.umanitoba.ca ([130.179.16.23]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IRb5x-0005aN-7a for emacs-orgmode@gnu.org; Sat, 01 Sep 2007 18:05:33 -0400 Received: from [192.168.1.113] (bas5-montreal02-1167961292.dsl.bell.ca [69.157.172.204]) (authenticated bits=0) by electra.cc.umanitoba.ca (8.13.0/8.13.0) with ESMTP id l81M5Ywx023405 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 1 Sep 2007 17:05:35 -0500 (CDT) In-Reply-To: <46D9DEE6.6060503@cc.umanitoba.ca> 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: emacs-orgmode Brian van den Broek said unto the world upon 09/01/2007 05:51 PM: Hi all, Sorry for the self-reply, but after posting I expanded the parameters of my google search, and thought a follow-up worthwhile. I posted woes regarding #+ARCHIVE lines getting archived or left behind. And I suggested a dummy headline to ameliorate the problem: > As I understand org-mode, this is a consequence of taking a subtree of > level n to continue until a headline of level m, m <= n occurs or EOF. > But, unless I am missing something, I don't see how the multiple > #+ARCHIVE lines technique can be made to work with this definition, > short of including dummy level 1 headlines in the file to `protect' the > #+ARCHIVE lines. (I mean something like inserting > > * To make org happy > #+ARCHIVE: ./_testofarchiveARCHIVE.org::* Third > > between * Second 2007 and * Third 2007.) In a thread from 2007-03 started by a similar problem was discussed regarding #+CATEGORY lines. Carsten said that what I called `dummy' headlines was one of two possible work-arounds he could see. What didn't come up was the suggestion I made: > It seems to me that a possible fix would be to look at the end of any > subtree that is being archived, and leave behind an #+ARCHIVE line (or > perhaps uninterrupted block of #+ lines) that terminates the tree being > archived. Now I am curious as to if this is unworkable. Carsten, if it is, would you mind briefly sketching why? (Time permitting, of course.) Thanks and best, Brian vdB