From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible to exclude/include tags for agenda custom commands?
Date: Sun, 23 Feb 2020 12:55:57 -0800 [thread overview]
Message-ID: <87ftf1xbtu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87mu994ete.fsf@gnu.org> (Bastien's message of "Sun, 23 Feb 2020 14:24:13 +0100")
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
Bastien <bzg@gnu.org> writes:
> Hi Eric,
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I hope that helps!
>
> thanks for the detailed example. What verison of Org and Emacs?
>
> With your example and Org mode version 9.3.6 and GNU Emacs 28.0.50
> I don't get the warning. If you have a ECM I'm willing to test more.
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.
Steps to reproduce:
1. emacs -Q
2. Add Org of your choice to load-path
3. Load the attached startup.el
4. Make sure the attached test.org is someplace where the previous file
can find it.
5. org-agenda, then the "b" key
6. Hit "g" or "r", either will trigger the warning
Hope that works,
Eric
[-- Attachment #2: startup.el --]
[-- Type: text/plain, Size: 246 bytes --]
(setq org-agenda-custom-commands
'(("b" "Bugs?"
((agenda ""
((org-agenda-start-day "2020-02-22")
(org-agenda-span 10))))
((org-agenda-tag-filter '("+buggy"))))))
(setq org-agenda-files '("~/test.org")
org-agenda-sticky t)
[-- Attachment #3: test.org --]
[-- Type: application/vnd.lotus-organizer, Size: 97 bytes --]
next prev parent reply other threads:[~2020-02-23 20:56 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 [this message]
2020-02-24 9:14 ` Bastien
2020-02-24 17:03 ` Eric Abrahamsen
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=87ftf1xbtu.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).