emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Org Mode <emacs-orgmode@gnu.org>, Christopher Witte <chris@witte.net.au>
Subject: Re: Visibility cycling with inline tasks
Date: Wed, 19 Sep 2012 12:59:19 +0200	[thread overview]
Message-ID: <AEF00FC9-5C3B-4744-B23B-AE40D935D915@gmail.com> (raw)
In-Reply-To: <87ehlypags.fsf@bzg.ath.cx>

On 19 sep. 2012, at 12:34, Bastien <bzg@altern.org> wrote:

> Hi Christopher,
> Christopher Witte <chris@witte.net.au> writes:
>> I have a document with lots of inline tasks scattered throughout it. I
>> want to get an overview of the document so I use S-<TAB> to cycle to
>> CONTENTS, when I do that all of the inline tasks are displayed like
>> this:
> You can add this hook:
> (add-hook 'org-cycle-hook
>  (lambda (state) (when (eq state 'contents) (hide-sublevels 6))))
>> Should this be the default? Is this also the behaviour that other
>> people expect?
> I tend to think this should be the default but I'm not using inline
> tasks at all, so I'll wait other users' feedback on this.

I agree that this would be a good default, but not with a hard-coded 6.

(add-hook 'org-cycle-hook
 (lambda (state) (when (eq state 'contents)
		   (and (boundp 'org-inlinetask-min-level)
			(hide-sublevels (1- org-inlinetask-min-level))))))

And it is probably better to wrap this into a function and add that function
to the default value of org-cycle-hook, after org-cucle-hide-drawers

- Carsten

  reply	other threads:[~2012-09-19 11:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 13:38 Visibility cycling with inline tasks Christopher Witte
2012-09-19 10:34 ` Bastien
2012-09-19 10:59   ` Carsten Dominik [this message]
2012-09-22  9:02     ` Bastien
2012-09-22  9:03       ` Carsten Dominik
2012-09-23  7:55         ` Christopher Witte

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:

  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=AEF00FC9-5C3B-4744-B23B-AE40D935D915@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bzg@altern.org \
    --cc=chris@witte.net.au \
    --cc=emacs-orgmode@gnu.org \


* 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


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).