Re: [O] Bug: org-sparse-tree property broken [8.0.7 (8.0.7-14-g22b447-elpa @ /home/mboes/.emacs.d/elpa/org-20130902/)]
Hi Mathieu, thank you for your report - I have fixed this issue. Regards - Carsten On 6.9.2013, at 09:16, Mathieu Boespflug mb...@tweag.net wrote: Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. [Sample org file at the end of this email.] Creating a sparse tree with org-sparse-tree and then selecting [p] property does not work. e.g. when selecting ARCHIVE_OLPATH as the property and Projects/Project1 as the value in the sample file below. Expected behaviour: a sparse tree is shown in the buffer containing only the matching headlines. Actual behaviour: all subtrees get folded and that's it. Cycling the visibility of any subtree does not reveal further a sparse tree. * Archived tasks ** DONE Task 1 CLOSED: [2013-04-10 mer. 18:43] :LOGBOOK: - State DONE from NEXT [2013-04-10 mer. 18:43] :END: :PROPERTIES: :ARCHIVE_TIME: 2013-09-05 jeu. 23:24 :ARCHIVE_FILE: ~/org/org.org :ARCHIVE_OLPATH: Projects/Project1 :ARCHIVE_CATEGORY: org :ARCHIVE_TODO: DONE :END: ** DONE Task 2 CLOSED: [2013-04-22 lun. 14:12] :LOGBOOK: - State DONE from TODO [2013-04-22 lun. 14:12] :END: :PROPERTIES: :ARCHIVE_TIME: 2013-09-05 jeu. 23:25 :ARCHIVE_FILE: ~/org/org.org :ARCHIVE_OLPATH: Projects/Project2 :ARCHIVE_CATEGORY: org :ARCHIVE_TODO: DONE :END: Emacs : GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2) of 2013-08-07 on -mnt-storage-buildroots-staging-x86_64-eric Package: Org-mode version 8.0.7 (8.0.7-14-g22b447-elpa @ /home/mboes/.emacs.d/elpa/org-20130902/) signature.asc Description: Message signed with OpenPGP using GPGMail
[O] Bug: org-sparse-tree property broken [8.0.7 (8.0.7-14-g22b447-elpa @ /home/mboes/.emacs.d/elpa/org-20130902/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. [Sample org file at the end of this email.] Creating a sparse tree with org-sparse-tree and then selecting [p] property does not work. e.g. when selecting ARCHIVE_OLPATH as the property and Projects/Project1 as the value in the sample file below. Expected behaviour: a sparse tree is shown in the buffer containing only the matching headlines. Actual behaviour: all subtrees get folded and that's it. Cycling the visibility of any subtree does not reveal further a sparse tree. * Archived tasks ** DONE Task 1 CLOSED: [2013-04-10 mer. 18:43] :LOGBOOK: - State DONE from NEXT [2013-04-10 mer. 18:43] :END: :PROPERTIES: :ARCHIVE_TIME: 2013-09-05 jeu. 23:24 :ARCHIVE_FILE: ~/org/org.org :ARCHIVE_OLPATH: Projects/Project1 :ARCHIVE_CATEGORY: org :ARCHIVE_TODO: DONE :END: ** DONE Task 2 CLOSED: [2013-04-22 lun. 14:12] :LOGBOOK: - State DONE from TODO [2013-04-22 lun. 14:12] :END: :PROPERTIES: :ARCHIVE_TIME: 2013-09-05 jeu. 23:25 :ARCHIVE_FILE: ~/org/org.org :ARCHIVE_OLPATH: Projects/Project2 :ARCHIVE_CATEGORY: org :ARCHIVE_TODO: DONE :END: Emacs : GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2) of 2013-08-07 on -mnt-storage-buildroots-staging-x86_64-eric Package: Org-mode version 8.0.7 (8.0.7-14-g22b447-elpa @ /home/mboes/.emacs.d/elpa/org-20130902/)
Re: [O] Bug: org-sparse-tree property broken [8.0.7 (8.0.7-14-g22b447-elpa @ /home/mboes/.emacs.d/elpa/org-20130902/)]
Hi Mathieu, Mathieu Boespflug mb...@tweag.net writes: Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. I confirm the bug: but it only happens when the query string contains a /, as this will parsed further as meaning the slash is followed by a TODO keyword. I cannot think of a simple fix right now, but this should be fixed for sure. Thanks for reporting this, -- Bastien