From: Kyle Meyer <kyle@kyleam.com>
To: Lem Ming <ramboman777@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Bug: org-agenda-filter-by-top-heading does not filter [9.1.14 (release_9.1.14-908-gf1269e)]
Date: Sun, 16 Sep 2018 16:29:48 -0400 [thread overview]
Message-ID: <87efdtw5hf.fsf@kyleam.com> (raw)
In-Reply-To: <CAOQj6-AyxHz-23n9BZXVDVPKpckYrt0PQwQDYHpfabSgnqWiVA@mail.gmail.com>
Hello,
Lem Ming <ramboman777@gmail.com> writes:
> In the agenda list `org-agenda-list` buffer, when I do
> `org-agenda-filter-by-top-headline` when the point is over a line with a
> headline, nothing is filtered.
>
I've never used org-agenda-filter-by-top-headline, but taking a quick
look at it and its helper, org-find-top-headline, the intention seems to
be to find the level-one parent of the current heading. So, in your
example,
> * Root
> ** TODO task 2
> :tag_2:
> DEADLINE: <2018-09-14 Fri 12:00:00>
> :PROPERTIES:
> :ADD_TIME: <2018-09-07 Fri 23:47:00>
> :END:
> *** TODO task 2.1
> DEADLINE: <2018-09-14 Fri 11:00:00>
> :PROPERTIES:
> :ADD_TIME: <2018-09-07 Fri 23:47:00>
> :END:
[...]
> ** TODO task 7
> DEADLINE: <2018-09-14 Fri 12:00:00> SCHEDULED: <2018-09-12 Wed 10:00:00>
... it'd find "Root" if point were on any of the tasks. If I'm reading
your report correctly, you're assuming that with point on the "task 2",
it'd take *that* as the top-level heading and filter to all the tasks
under it (task 2.1, etc). Instead, it finds "Root" and filters to
everything thing under that, which---in your example file---is the same
thing, so you don't see any change.
--
Kyle
next prev parent reply other threads:[~2018-09-16 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:53 Bug: org-agenda-filter-by-top-heading does not filter [9.1.14 (release_9.1.14-908-gf1269e)] Lem Ming
2018-09-14 5:02 ` Lem Ming
2018-09-16 20:29 ` Kyle Meyer [this message]
2018-09-22 17:57 ` Adrian Bradd
2018-09-29 15:37 ` Lem Ming
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=87efdtw5hf.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=ramboman777@gmail.com \
/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).