From: Marc-Oliver Ihm <marc-oliver.ihm@online.de>
To: emacs-orgmode@gnu.org
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Visibilty of inline tasks
Date: Mon, 06 Feb 2012 20:23:32 +0100 [thread overview]
Message-ID: <4F3028B4.9090306@online.de> (raw)
In-Reply-To: <80d3p17ss3.fsf@missioncriticalit.com>
Am 16.12.2010 14:26, schrieb Sébastien Vauban:
> Hello,
>
> 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?
>
> Best regards,
> Seb
>
Hello all,
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.
with kind regards, Marc-Oliver Ihm
(And sorry for not beeing able to see the immediate elisp-cause of the problem !)
next prev parent reply other threads:[~2012-02-06 19:23 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 [this message]
2012-02-06 20:34 ` Sebastien Vauban
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=4F3028B4.9090306@online.de \
--to=marc-oliver.ihm@online.de \
--cc=emacs-orgmode@gnu.org \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.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).