From: Colin Baxter <m43cap@yandex.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Keys to Category Filter Agenda
Date: Sat, 10 Dec 2022 11:24:58 +0000 [thread overview]
Message-ID: <87pmcrtsad.fsf@yandex.com> (raw)
In-Reply-To: <875yejsj62.fsf@localhost> (Ihor Radchenko's message of "Sat, 10 Dec 2022 09:27:17 +0000")
>>>>> Ihor Radchenko <yantar92@posteo.net> writes:
> Colin Baxter <m43cap@yandex.com> writes:
>> In agenda, you can filter by category by pressing '<' when point
>> on that particular category. To remove filtering, press '<'
>> again. All this is explained in the org-mode info. However the
>> initial agenda buffer, viewed by 'C-c a', gives the keys '<' for
>> filtering but '>' to remove the restriction. This surely is wrong
>> since '>' is the key to call the org-agenda-date-prompt, or am I
>> missing something very basic here?
> You are misunderstanding agenda buffer and the initial agenda
> dialog. The former is where "<" acts as category filter. The
> dialog uses "<" to set agenda restriction, as it is explained in
> the dialog message.
Indeed. I understand that, but the question was about '>' not '<'. The
initial agenda buffer has
< Buffer, subtree/region restriction
> Remove restriction
If I remove the restriction with >, as suggested by the initial buffer,
I get the date prompt. I have to enter either '<' again or '|' to clear
the restrictions. This information is given only in org-mode info not in
the initial agenda buffer.
Best wishes,
next prev parent reply other threads:[~2022-12-10 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:17 Keys to Category Filter Agenda Colin Baxter
2022-12-10 9:27 ` Ihor Radchenko
2022-12-10 11:24 ` Colin Baxter [this message]
2022-12-10 11:33 ` Ihor Radchenko
2022-12-13 11:53 ` Colin Baxter
2022-12-13 11:59 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmcrtsad.fsf@yandex.com \
--to=m43cap@yandex.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.