From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Visibilty of inline tasks
Date: Mon, 06 Feb 2012 21:34:28 +0100 [thread overview]
Message-ID: <80r4y7r99n.fsf@somewhere.org> (raw)
In-Reply-To: 4F3028B4.9090306@online.de
Hi Marc-Oliver,
Marc-Oliver Ihm wrote:
> Am 16.12.2010 14:26, schrieb Sébastien Vauban:
>> Though that is written in =org-inlinetask.el=:
>>
>> ;; Visibility cycling exempts these nodes from cycling. So whenever their
>> ;; parent is opened, so are these tasks.
>>
>> I have the impression that, up to a couple of days ago, the inlined headlines
>> were showed in the =children= view, such as:
>>
>> --8<---------------cut here---------------start------------->8---
>> * TODO Write document
>> ** TODO Write intro
>> ** TODO Write code
>> *************** WAIT Ask the client about specs
>> ** TODO Write conclusion
>> --8<---------------cut here---------------end--------------->8---
>>
>> Am I right?
>>
>> - If yes, could it be back like that?
>> - If no, would others as well be interested in such a behavior?
>
> as far as I can see, Sebastien description still applies. This behaviour
> (bug ?) makes it hard to work with inline-tasks (which I do alot), because
> once I open the topmost node, all subheadings with any inline task are
> opened too, regardless how depp they are nested. This makes it nearly
> impossible to get an overview about the contents of the node.
>
> So: This problem still seems to be around.
What I described was the impression that:
- before December, inline tasks were shown when TAB'ing
- at some point in December, they were not anymore. That's wrong. And I had
mixed impressions because I saw them when C-c / t'ing for tasks inside a
document.
In fact, I share your point of view: as they don't participate to document
structure (that's why they're inline tasks), they should not be made visible
when cycling. That's not the current behavior.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-02-06 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 13:26 Visibilty of inline tasks Sébastien Vauban
2012-02-06 19:23 ` Marc-Oliver Ihm
2012-02-06 20:34 ` Sebastien Vauban [this message]
2012-02-08 21:06 ` [bug ? regression ?] " Marc-Oliver Ihm
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=80r4y7r99n.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 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).