all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Meir Goldenberg <mgoldenbe@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: A bug with expanding headlines of the sparse tree?
Date: Tue, 11 Aug 2015 15:07:19 +0200	[thread overview]
Message-ID: <87egja7z3s.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAP1Du3Vm58iW5Y5tA6EJAJTiSRV8sOnWfjytQnR0kyga5DBo=Q@mail.gmail.com> (Meir Goldenberg's message of "Thu, 6 Aug 2015 15:49:59 +0300")

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

  reply	other threads:[~2015-08-11 13:05 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 [this message]
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
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=87egja7z3s.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mgoldenbe@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 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.