From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: subtree archiving when Archive is not final headline yields bad visibility [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2+gg1+12/lisp/org/)] Date: Mon, 11 Dec 2017 15:10:19 +0100 Message-ID: <87po7lxsms.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52484) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOOml-0004MP-5t for emacs-orgmode@gnu.org; Mon, 11 Dec 2017 09:10:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eOOmk-00007Y-Ap for emacs-orgmode@gnu.org; Mon, 11 Dec 2017 09:10:23 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:53572) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eOOmk-00006S-4g for emacs-orgmode@gnu.org; Mon, 11 Dec 2017 09:10:22 -0500 In-Reply-To: (Allen Li's message of "Thu, 7 Dec 2017 12:52:05 -0800") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Allen Li Cc: emacs-orgmode@gnu.org Hello, Allen Li writes: > On Wed, Dec 6, 2017 at 12:19 PM, Allen Li wrote: >> (Can reproduce with Org 9.1.3, submitting with emacs -Q) >> >> Using a file tmp.org: >> >> * Foo >> ** Archive :ARCHIVE: >> *** Test >> :PROPERTIES: >> :ARCHIVE_TIME: 2017-12-06 Wed 12:13 >> :END: >> ** Bar >> >> This appears like so with default visibility: >> >> * Foo >> ** Archive :ARCHIVE:... >> ** Bar >> >> Archiving Bar with C-c C-x A yields: >> >> * Foo >> ** Archive :ARCHIVE:... >> *** Bar... >> >> Expected visibility: >> >> * Foo >> ** Archive :ARCHIVE:... AFAICT, the action leaves point on the just archived sub-heading. As a consequence, it has to visible. Your expected visibility means the function should move point. Why would that be better than letting it on the headline you just operated on? >> AFAIK, there is no special location in the file for archived subtrees, >> i.e., there is nothing wrong with >> >> * Some projects >> ** Some item... >> ** Archive :ARCHIVE:... >> ** New entry... > > This bug means that the Archive headline's position is significant. I fail to see how you draw such a conclusion. Regards, -- Nicolas Goaziou