From: Miro Bezjak <bezjak.miro@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: multiple agenda custom commands causes tag-filter-preset not to work?
Date: Sat, 7 Dec 2013 22:14:48 +0100 [thread overview]
Message-ID: <CAMJqDfPQRMg2-RDA5PFtf2XaKKhdpE_ESa8G3ntph1WHDfyJmQ@mail.gmail.com> (raw)
In-Reply-To: <87zjoe59wi.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
Hi Bastien,
thank you for the explanation.
I've implemented the solution to my problem by using `agenda-skip-entry-if'
instead of `org-agenda-tag-filter-preset'.
Example:
------------------------------------------------------------
(setq org-agenda-custom-commands
'(("h" "home"
((agenda "" ((org-agenda-span 'day)
(org-agenda-skip-function '(org-agenda-skip-entry-if
'regexp ":work:"))))
(alltodo)))))
------------------------------------------------------------
Kind Regards,
Miro
On Fri, Dec 6, 2013 at 3:30 PM, Bastien <bzg@gnu.org> wrote:
> Hi Miro,
>
> Miro Bezjak <bezjak.miro@gmail.com> writes:
>
> > It appears that `org-agenda-tag-filter-preset' does not work when I
> > define
> > multiple commands under one. The agenda is rendered as if filter was
> > never set.
> >
> > On the other hand, if I remove `(alltodo)', thus defining only the
> > agenda, then
> > the filter works without problems.
>
> Yes, that's by design -- or more precisely, by lack of a good way to
> filter agenda blocks.
>
> HTH,
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 1854 bytes --]
next prev parent reply other threads:[~2013-12-07 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:23 multiple agenda custom commands causes tag-filter-preset not to work? Miro Bezjak
2013-11-27 10:23 ` Miro Bezjak
2013-11-28 16:27 ` Miro Bezjak
2013-11-28 17:46 ` Bastien
2013-12-06 14:30 ` Bastien
2013-12-07 21:14 ` Miro Bezjak [this message]
2014-01-04 14:33 ` 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=CAMJqDfPQRMg2-RDA5PFtf2XaKKhdpE_ESa8G3ntph1WHDfyJmQ@mail.gmail.com \
--to=bezjak.miro@gmail.com \
--cc=bzg@gnu.org \
--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).