all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Meir Goldenberg <mgoldenbe@gmail.com>
To: Meir Goldenberg <mgoldenbe@gmail.com>, Bastien <bzg@gnu.org>,
	emacs-orgmode@gnu.org
Subject: Re: A bug with expanding headlines of the sparse tree?
Date: Mon, 24 Aug 2015 10:34:22 +0300	[thread overview]
Message-ID: <CAP1Du3W39f8u+i8jbxfAomJDUdp8MyvAPJD-gOPaKbLKKNGd1Q@mail.gmail.com> (raw)
In-Reply-To: <87k2sly6xj.fsf@nicolasgoaziou.fr>

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

Why not just have a command to exit the sparse tree mode?

On Mon, Aug 24, 2015 at 1:30 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Meir Goldenberg <mgoldenbe@gmail.com> writes:
>
> > I am running on 8.3.1 and am getting the same behavior. In fact, when I
> run
> > on the simple example from my original message, the heading marked FUTURE
> > does not get hidden to start with.
>
> Top level headlines are never hidden.
>
> Admittedly, this defeats the purpose of a sparse tree if all the
> information you need to filter out is located in such constructs.
> However, hiding them would make a view from which it would be difficult
> to recover from.
>
> Regards,
>

[-- Attachment #2: Type: text/html, Size: 1094 bytes --]

  reply	other threads:[~2015-08-24  7:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 12:49 A bug with expanding headlines of the sparse tree? Meir Goldenberg
2015-08-11 13:07 ` Nicolas Goaziou
2015-08-11 19:16   ` Meir Goldenberg
2015-08-11 22:56     ` Nicolas Goaziou
2015-08-12  8:25       ` Meir Goldenberg
2015-08-12 13:03         ` Nicolas Goaziou
2015-08-18 15:32 ` Bastien
2015-08-23 15:26   ` Meir Goldenberg
2015-08-23 22:30     ` Nicolas Goaziou
2015-08-24  7:34       ` Meir Goldenberg [this message]
2015-08-27 18:18         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP1Du3W39f8u+i8jbxfAomJDUdp8MyvAPJD-gOPaKbLKKNGd1Q@mail.gmail.com \
    --to=mgoldenbe@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.