From: Matthew Lundin <mdl@imapmail.org>
To: buckbrody@gmail.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: due today notification
Date: Wed, 28 Apr 2010 16:38:05 -0400 [thread overview]
Message-ID: <87mxwnuxci.fsf@fastmail.fm> (raw)
In-Reply-To: <p2l8bd4668a1004281314ib1e86e23i1049c33f76a586d8@mail.gmail.com> (Buck Brody's message of "Wed, 28 Apr 2010 16:14:22 -0400")
Buck Brody <buckbrody@gmail.com> writes:
> The problem with the sparse tree is that a sparse tree will only show
> the headlines above the item with a deadline, it will not show the
> sibling headlines. For example, if I used a sparse tree on:
That depends on the value of org-show-siblings.
To ensure that siblings are visible, you can use a simple setting such
as:
(setq org-show-siblings t)
Type C-h v org-show-hierarchy-above [RET] for more fine-grained
customization options.
With org-show-siblings set to t, I see the following:
--8<---------------cut here---------------start------------->8---
* Fruit
** Apple
*** Macintosh
*** Crab
DEADLINE: <2010-04-28 Wed>
*** Golden delicious
** Vegetable
--8<---------------cut here---------------end--------------->8---
Best,
Matt
> * Fruit
> ** Apple
> *** Macintosh
> *** Crab
> DEADLINE: <2010-04-28 Wed>
> *** Golden delicious
> ** Vegetable
> *** lettuce
> *** squash
> *** cucumber
>
> It would look like
>
> * Fruit
> *** Crab
> DEADLINE: <2010-04-28 Wed>
next prev parent reply other threads:[~2010-04-28 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 17:12 due today notification Buck Brody
2010-04-23 22:54 ` Matt Lundin
2010-04-26 16:48 ` Buck Brody
2010-04-27 19:01 ` Matthew Lundin
2010-04-28 19:12 ` Buck Brody
2010-04-28 19:57 ` Matthew Lundin
2010-04-28 20:14 ` Buck Brody
2010-04-28 20:38 ` Matthew Lundin [this message]
2010-04-28 20:46 ` Nick Dokos
2010-04-28 21:29 ` Buck Brody
2010-04-28 22:34 ` Nick Dokos
2010-04-24 7:40 ` Bastien
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=87mxwnuxci.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=buckbrody@gmail.com \
--cc=emacs-orgmode@gnu.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).