emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: John Wiegley <johnw@gnu.org>
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: Thu, 15 Jun 2023 10:12:33 +0000	[thread overview]
Message-ID: <87o7lh590u.fsf@localhost> (raw)
In-Reply-To: <m2a5x1hqks.fsf@newartisans.com>

John Wiegley <johnw@gnu.org> writes:

> Since the documentation also mentions that space means “any tag”, I guess now
> it’s a design question: Should <space> mean “no tags” or “any tag”? I feel
> like it should mean “no tag” only because you also use space to clear all tags
> in the agenda after pressing “:”.
>
> If the decision is “desired behavior”, then the muscle memory needed is
> ‘\ - <space>‘ rather than ‘\ <space>‘. Still feels odd for space to mean
> anything rather than nothing, though… I mean, space is empty, right? :)

Yeah. I checked the manual, and we have SPC being "any tag at all" since
the very beginning of the git history:

  #+findex: org-agenda-filter-by-tag
  Filter the agenda view with respect to a tag.  You are prompted for
  a tag selection letter; {{{kbd(SPC)}}} means any tag at all.

Upon seeing the manual, I am inclined to keep the current behaviour,
unless we have other voices supporting the change.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-06-15 10:08 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
2023-06-14 18:00         ` John Wiegley
2023-06-15 10:12           ` Ihor Radchenko [this message]
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=87o7lh590u.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=johnw@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).