emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Mathieu Boespflug <mboes@tweag.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-sparse-tree property broken [8.0.7 (8.0.7-14-g22b447-elpa @ /home/mboes/.emacs.d/elpa/org-20130902/)]
Date: Sun, 8 Sep 2013 08:58:27 +0200	[thread overview]
Message-ID: <5D8A33FE-FEA4-4EF1-B96C-60123CDEB91E@gmail.com> (raw)
In-Reply-To: <CAC0LnfuG-Q7+GzjU1FTimZ8iZ08AwgeWWXqVrBFy684L3wFO4Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]

Hi Mathieu,

thank you for your report - I have fixed this issue.

Regards

- Carsten

On 6.9.2013, at 09:16, Mathieu Boespflug <mboes@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/)
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

      parent reply	other threads:[~2013-09-08  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06  7:16 Bug: org-sparse-tree property broken [8.0.7 (8.0.7-14-g22b447-elpa @ /home/mboes/.emacs.d/elpa/org-20130902/)] Mathieu Boespflug
2013-09-06 14:03 ` Bastien
2013-09-08  6:58 ` Carsten Dominik [this message]

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=5D8A33FE-FEA4-4EF1-B96C-60123CDEB91E@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mboes@tweag.net \
    /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).