emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Tue, 13 Dec 2022 11:53:52 +0000	[thread overview]
Message-ID: <87tu1zplin.fsf@yandex.com> (raw)
In-Reply-To: <87fsdnfq7a.fsf@localhost> (Ihor Radchenko's message of "Sat, 10 Dec 2022 11:33:45 +0000")

>>>>> Ihor Radchenko <yantar92@posteo.net> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> 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.

    > Initial prompt buffer only describes bindings for that buffer.
    > They are totally different from agenda-mode buffer.

That is not correct for the '<' key. You are told "Restriction is only
possible in Org buffers". In my opinion the distinction of the '<' key
should be more positively indicated. The wording and arrangement of the
prompt buffer is confusing at best. It is disheartening when the
difficulties experienced by a non-specialist seem to be dismissed
out-of-hand.

Best wishes,


  reply	other threads:[~2022-12-13 11:55 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
2022-12-10 11:33     ` Ihor Radchenko
2022-12-13 11:53       ` Colin Baxter [this message]
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

  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=87tu1zplin.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 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).