From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: A bug with expanding headlines of the sparse tree?
Date: Tue, 11 Aug 2015 15:07:19 +0200
Message-ID: <87egja7z3s.fsf@nicolasgoaziou.fr>
References: <CAP1Du3Vm58iW5Y5tA6EJAJTiSRV8sOnWfjytQnR0kyga5DBo=Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33490)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZP9FW-0007AN-U0
	for emacs-orgmode@gnu.org; Tue, 11 Aug 2015 09:05:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZP9FQ-00034m-Az
	for emacs-orgmode@gnu.org; Tue, 11 Aug 2015 09:05:50 -0400
Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:60969)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZP9FQ-00033R-2l
	for emacs-orgmode@gnu.org; Tue, 11 Aug 2015 09:05:44 -0400
In-Reply-To: <CAP1Du3Vm58iW5Y5tA6EJAJTiSRV8sOnWfjytQnR0kyga5DBo=Q@mail.gmail.com>
	(Meir Goldenberg's message of "Thu, 6 Aug 2015 15:49:59 +0300")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Meir Goldenberg <mgoldenbe@gmail.com>
Cc: emacs-orgmode@gnu.org

Hello,

Meir Goldenberg <mgoldenbe@gmail.com> writes:

> I am using org-mode 8.2.10. Suppose we have this:
>
> * TODO Task1 [0/1]
> SCHEDULED: <2015-08-09 Sun>
> - [ ] Buy bread
> * FUTURE Task2
>
> Now, if we do C-/ T and give TODO for the keyword, then we correctly get:
>
> * TODO Task1 [0/1]...
>
> However, if we press Tab on this line, then the whole content, including
> next headline (the one marked FUTURE) shows up, which seems to be
> wrong.

This is to be expected. TAB discloses the entry and all children. It
also leaves the entry in an editable state. What you suggest gives

  * TODO Task1 [0/1]
  SCHEDULED: <2015-08-09 Sun>
  - [ ] Buy bread...

which means 1. that you can't reach Task2 easily, 2. that you can't edit
plain list comfortably.

Regards,

-- 
Nicolas Goaziou