From: Carsten Dominik <dominik@science.uva.nl>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Custom filtering the agenda by (file) tag
Date: Wed, 5 Nov 2008 10:58:22 +0100 [thread overview]
Message-ID: <D9FA7948-A5C2-4609-8681-0063237F9019@uva.nl> (raw)
In-Reply-To: <2F829704-5F3A-4A73-BA9F-2D4CBA96AB5C@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2113 bytes --]
Sorry for following up on my own message.
On Nov 5, 2008, at 7:45 AM, Carsten Dominik wrote:
> Hi Rick,
>
> you would need to write your own skip function, using a call to
>
> (member "PERSONAL" (org-get-tags-at))
>
> HTH
>
> - Carsten
I am just realizing that you are using file tags. Which means
that you have your personal tags in a separate file. In this
case, you can get your agenda view considerably faster by writing
a custom agenda view that restricts the list of agenda files to
the personal one.
(org-add-agenda-custom-command
'("b" agenda "Personal Agenda"
((org-agenda-files '("~org/personal.org"))))
Another possibility is to use the normal agenda view and to use
filtering in the agenda with "/ p" (assuming that "p" is your
fast key to the PERSONAL tag). I myself have pretty much switched
to filtering and simplified my custom agenda commands accordingly.
HTH
- Carsten
>
>
> On Nov 5, 2008, at 12:18 AM, Rick Moynihan wrote:
>
>> Hi all,
>>
>> I've been setting up a whole bunch of org-agenda-custom-commands and
>> am having trouble setting up a filter to display ONLY items in the
>> agenda view which are tagged PERSONAL across all my org-agenda-files.
>>
>> I tried several ways to do this and ended up trying the following:
>>
>> (org-add-agenda-custom-command
>> '("b" agenda "Personal Agenda"
>> ((org-agenda-skip-function '(org-agenda-skip-subtree-if
>> 'notregexp ":PERSONAL:")))))
>>
>> Unfortunately this doesn't appear to work with FILETAGS as it relies
>> on matching against a regex. How can I implement this view with full
>> tag support and inheritance?
>>
>> Thanks again,
>>
>> R.
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[-- Attachment #1.2: Type: text/html, Size: 4141 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2008-11-05 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 23:18 Custom filtering the agenda by (file) tag Rick Moynihan
2008-11-05 6:45 ` Carsten Dominik
2008-11-05 9:58 ` Carsten Dominik [this message]
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=D9FA7948-A5C2-4609-8681-0063237F9019@uva.nl \
--to=dominik@science.uva.nl \
--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).