From: Hsiu-Khuern Tang <hsiu-khuern.tang@hp.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Searching SCHEDULED/DEADLINE properties turns up spurious headings
Date: Mon, 12 Jan 2009 09:50:17 -0800 [thread overview]
Message-ID: <20090112175017.GA24132@hplhtang1> (raw)
In-Reply-To: <411B5F54-4F10-43D6-A516-D11A51BCA5AD@uva.nl>
* On Sat 08:54PM +0000, 10 Jan 2009, Carsten Dominik (dominik@science.uva.nl) wrote:
> Hi Hsiu,
>
> I believe this is a misunderstanding. You are constructing
> a sparse tree. Sparse tree always show all top-level headlines.
> The search really only matches the second one, as you can see from
> the highlighted stars.
When I run that search (C-c \ +DEADLINE<="<2009-01-28>" <RET>), all the three
headlines have highlighted stars. (I am running Org-mode 6.17trans.)
> - Carsten
>
>
>
> On Jan 10, 2009, at 12:32 AM, Hsiu-Khuern Tang wrote:
>
> > I find that doing a tags search for SCHEDULED or DEADLINE turns up
> > headings
> > that do not have any schedule or deadlines.
> >
> > Using the example from http://article.gmane.org/gmane.emacs.orgmode/10274
> > :
> >
> > ,----
> > | #+SEQ_TODO: NEXT WAITING | DONE
> > | #+STARTUP: overview
> > |
> > | * DONE Test1
> > | CLOSED: [2009-01-07 Wed 12:26]
> > |
> > | * NEXT Test2
> > | DEADLINE: <2009-01-28 Wed>
> > |
> > | * Test3
> > `----
> >
> > If I type
> >
> > C-c \ +DEADLINE<="<2009-01-28>" <RET>
> >
> > all three headlines are selected! I expected to match the second
> > headline
> > only.
--
Best,
Hsiu-Khuern.
next prev parent reply other threads:[~2009-01-12 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 23:32 Searching SCHEDULED/DEADLINE properties turns up spurious headings Hsiu-Khuern Tang
2009-01-10 20:54 ` Carsten Dominik
2009-01-12 17:50 ` Hsiu-Khuern Tang [this message]
2009-01-13 9:35 ` Carsten Dominik
2009-01-13 18:06 ` Hsiu-Khuern Tang
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=20090112175017.GA24132@hplhtang1 \
--to=hsiu-khuern.tang@hp.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).