From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Possible to exclude/include tags for agenda custom commands?
Date: Mon, 24 Feb 2020 09:03:27 -0800 [thread overview]
Message-ID: <87tv3fx6hs.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87d0a4xs79.fsf@gnu.org
Bastien <bzg@gnu.org> writes:
> Hi Eric,
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> The key is having `org-agenda-sticky' set to t -- this means that we'll
>> let-bind buffer-local variables in a buffer where they're already
>> set.
>
> thanks for the reproducible example, I was able to get the warning.
>
> You can safely ignore it: when redoing sticky agenda, we need to
> let-bind the values as explicitely set in the agenda custom command
> (here the org-agenda-tag-filter value) while preparing the agenda
> requires the variables to be made local. I don't see what can be
> done and I don't think there hidden bugs lingering around here.
Okay! I also didn't think anything terrible was going on here. I note
there's the variable `org-agenda-doing-sticky-redo' that we could
presumably check, and avoid re-setting the tag filter when it's t, but
again I don't think the warning is a big deal.
Thanks,
Eric
prev parent reply other threads:[~2020-02-24 17:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 19:03 Possible to exclude/include tags for agenda custom commands? Stig Brautaset
2020-02-12 22:30 ` Bastien
2020-02-13 19:39 ` Stig Brautaset
2020-02-14 10:02 ` Bastien
2020-02-14 22:05 ` Adam Porter
2020-02-18 13:05 ` Bastien
2020-02-20 3:57 ` Adam Porter
2020-02-20 7:23 ` Bastien
2020-02-20 16:50 ` Eric Abrahamsen
2020-02-20 17:24 ` Bastien
2020-02-20 17:48 ` Eric Abrahamsen
2020-02-20 19:02 ` Eric Abrahamsen
2020-02-20 19:08 ` Bastien
2020-02-20 19:51 ` Eric Abrahamsen
2020-02-23 13:24 ` Bastien
2020-02-23 20:55 ` Eric Abrahamsen
2020-02-24 9:14 ` Bastien
2020-02-24 17:03 ` Eric Abrahamsen [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=87tv3fx6hs.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).