From: Bastien <email@example.com>
To: John Wiegley <firstname.lastname@example.org>
Cc: Dave Abrahams <email@example.com>, firstname.lastname@example.org
Subject: Re: Filtering agenda by the "top" category
Date: Tue, 10 Apr 2012 22:42:23 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (John Wiegley's message of "Wed, 04 Apr 2012 15:38:55 -0500")
John Wiegley <email@example.com> writes:
> I discovered the < key in the agenda yesterday (by accident!), which filters
> the Agenda down to entries having the same category.
> However, I use both *categories* and *projects*. For example:
> * Work
> :CATEGORY: Work
> :OVERLAY: (face (:background "#fdfdeb"))
> ** PROJECT Foo
> :CATEGORY: Foo
> I use :CATEGORY: for my project here so it shows up in the leftmost column of
> my agenda. I don't want every project displaying as just "Work". I use the
> :OVERLAY: so that all Work items have the same background color, which is a
> better way of seeing at a glance which *category* every item falls into.
> What this means is that although I can use < to filter by *project*, I can't
> filter down to the "Work" *category*. So that's what the code below does. I
> bind it to >, since I wasn't using what that binding does.
I tested the code and it looks useful.
Could you make a patch against current master?
> Also, I found a bug: passing a prefix argument to < doesn't have any effect.
> The code doesn't use that argument in any meaningful way.
This is now fixed. You can use `C-u <' to filter out the category of
the current line. Thanks for spotting this!
prev parent reply other threads:[~2012-04-10 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 20:38 Filtering agenda by the "top" category John Wiegley
2012-04-10 20:42 ` Bastien [this message]
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 \
* 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).