From: John Wiegley <johnw@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [POLL] [BUG] Inverse behavior from \ <space> [9.6.4 (release_9.6.4-1-g76cf21 @ /Users/johnw/.emacs.d/lisp/org-mode/lisp/)]
Date: Tue, 13 Jun 2023 22:22:29 -0700 [thread overview]
Message-ID: <m2edmemxd6.fsf@newartisans.com> (raw)
In-Reply-To: <87cz1zwux5.fsf@localhost> (Ihor Radchenko's message of "Tue, 13 Jun 2023 09:52:54 +0000")
>>>>> "IR" == Ihor Radchenko <yantar92@posteo.net> writes:
IR> Are you sure?
IR> I can see 124017b6d that changes
IR> (setq org-agenda-tag-filter
IR> (cons (concat (if exclude "-" "+") tag)
IR> current))
IR> to
IR> (setq org-agenda-tag-filter
IR> (cons (concat (if exclude "-" "+") tag)
IR> (if accumulate current nil)))
IR> The former would leave the current filter unchanged.
IR> It would be nice to bisect down to the commit that changed the behaviour.
IR> As it usually goes with agenda, consequences of some changes are not
IR> always straightforward.
Since my data should all still be compatible with the old version I was using,
I’ll see if I can bisect this. I know I was used to that binding, but I’m not
100% certain it wasn’t due to extenuating factors in my configuration.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2023-06-14 5:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 4:49 [BUG] Inverse behavior from \ <space> [9.6.4 (release_9.6.4-1-g76cf21 @ /Users/johnw/.emacs.d/lisp/org-mode/lisp/)] John Wiegley
2023-06-12 10:10 ` [POLL] " Ihor Radchenko
2023-06-12 19:48 ` John Wiegley
2023-06-13 9:52 ` Ihor Radchenko
2023-06-14 5:22 ` John Wiegley [this message]
2023-06-14 18:00 ` John Wiegley
2023-06-15 10:12 ` Ihor Radchenko
2023-08-16 12:06 ` Ihor Radchenko
2023-08-16 17:11 ` John Wiegley
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=m2edmemxd6.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).