From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Allen Li <vianchielfaura@gmail.com>
Cc: emacs-orgmode@gnu.org
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 [thread overview]
Message-ID: <87po7lxsms.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJr1M6ddzBqE5hVe4-R93o2SeOaQTYkNsQvQNmcYKNxeJgjMxw@mail.gmail.com> (Allen Li's message of "Thu, 7 Dec 2017 12:52:05 -0800")
Hello,
Allen Li <vianchielfaura@gmail.com> writes:
> On Wed, Dec 6, 2017 at 12:19 PM, Allen Li <vianchielfaura@gmail.com> 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
next prev parent reply other threads:[~2017-12-11 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 20:19 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/)] Allen Li
2017-12-07 20:52 ` Allen Li
2017-12-11 14:10 ` Nicolas Goaziou [this message]
2017-12-11 19:39 ` Allen Li
2017-12-11 22:32 ` Nicolas Goaziou
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=87po7lxsms.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=vianchielfaura@gmail.com \
/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).