From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: archival mirroring source headline structure? Date: Mon, 9 Jun 2008 12:52:03 +0100 Message-ID: <20080609115203.GA19192@atlantic.linksys.moosehall> References: <20080602163530.GC14400@atlantic.linksys.moosehall> <9592BB6CDB1CEB48826BE86ACD71FA996ABF63@kwik.ic.uva.nl> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K5fv3-0005Zh-Ue for emacs-orgmode@gnu.org; Mon, 09 Jun 2008 07:52:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K5fuy-0005Ye-Nc for emacs-orgmode@gnu.org; Mon, 09 Jun 2008 07:52:11 -0400 Received: from [199.232.76.173] (port=33339 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K5fuy-0005YQ-E9 for emacs-orgmode@gnu.org; Mon, 09 Jun 2008 07:52:08 -0400 Received: from mail.beimborn.com ([70.84.38.100]:40956) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K5fux-0002kv-RG for emacs-orgmode@gnu.org; Mon, 09 Jun 2008 07:52:08 -0400 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id m59Bq5Yl000576 for ; Mon, 9 Jun 2008 06:52:05 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id m59Bq4UF000569 for emacs-orgmode@gnu.org; Mon, 9 Jun 2008 12:52:04 +0100 Content-Disposition: inline In-Reply-To: <9592BB6CDB1CEB48826BE86ACD71FA996ABF63@kwik.ic.uva.nl> 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: org-mode mailing list On Mon, Jun 09, 2008 at 09:01:22AM +0200, Dominik, C. wrote: > Hi Adam, > > I agree that this would be nice, but I believe it is almost impossible > to make this stable. Because the user is free to add to and change > the tree in the Org buffer, it is very easy to break this mechanism. If I understand you correctly, I don't actually view this as breakage. If I have * A ** B ** C and I archive B, then rename A to D, then archive C, my archive file becomes: * A ** B * D ** C which is exactly what I want. Likewise if I were to relocate A to a different level rather than rename it. Am I missing something? I'll try `org-agenda-archive-to-archive-sibling' as suggested by Manuel. Incidentally I notice that this function appears to be undocumented. Thanks both!