Re: One vs many directories

[Ihor Radchenko]

> Sorry for that vague expression. Let us say I open Completions buffer
> I can switch into it, inspect it, ask for defined keys, evaluate with
> M-:, Emacs allows me to remain in the window and go to other
> window. Agenda buffer does not do that, this is probably because it
> just waits for any key and does not allow anything else. That means I
> will open Agenda and I cannot switch to other window, so I will close
> agenda to switch. Maybe I have 10 TODO keywords, I have to open file,
> I open Agenda again, aha, T... then close agenda, open file see
> keyword, then open agenda again. Repetitions without end and user is
> unable to use multiple windows. This really need not be so.

It appears to me (correct me if I am wrong) that you haven't tried
agenda multi-occur/keyword/etc searches. The way it works is that you
only need to select type of search from agenda dispatcher window (the
one you are criticising). Later, when you actually enter the search
string, you are left with an ordinary Emacs prompt. You are free to
leave the minibuffer and switch to other buffers searching for the
keywords you are interested in.

In general, there are two types of agenda searches available from agenda
dispatcher:
1. Most are free-hand searches where you need to type a search string:
   - match TAGS/PROP/TODO query
   - search for keywords
   - multi-occur
   - first two searches, but limited only to TODO tasks
2. Pre-defined searches where search string was set in advance (by
   developers or by user via org-agenda-custom-commands):
   - agenda listing tasks relevant to current week or day
   - all TODO entries
   - FLAGGED entries
   - stuck projects

The first type will let you leave search prompt as soon as you select
what type of search you are about to enter.
The second type does not really need entering any extra text - it is
predefined.

> You know how agenda is made like the 1985 BASIC menu in Commodore
> C=64, but even back then there was better interface for such menus.

FYI. Transient.el - menu dispatcher in popular magit package also does
not let you switch buffers. So, apparently many people would not agree
that it is so terrible design.

P.S. Nothing prevents you from calling, i.e. M-x org-occur or binding it
to a key of your choice.

Best,
Ihor

Jean Louis <bugs@gnu.support> writes:

> * Ihor Radchenko <yantar92@gmail.com> [2020-11-25 14:48]:
>> > When I do C-c a it runs (org-agenda) but I do not have "g" and I am on
>> > development version. The C-c a window is made so that I cannot go with
>> > cursor inside and that I cannot even expect the key map neither invoke
>> > command by M-x and I cannot even M-:
>> 
>> C-c a will first show so-called agenda dispatcher asking you what kind
>> of agenda view you want to get. You need to press a key according to
>> the popup window (i.e. `t' to see all not done items). Then, you will
>> get the proper agenda buffer with all the keymaps set and `g' bound to
>> refreshing the chosen agenda view in the buffer.
>> 
>> > All that is wrong and not aligned to Emacs common interface. It is bug
>> > that bugs. Agenda buffer should allow users those standard Emacs
>> > features.
>> 
>> I am wondering what is the common Emacs interface you refer to. I am not
>> aware about any standard way to prompt user while also showing detailed
>> description of what to expect from different choices.
>
> Sorry for that vague expression. Let us say I open Completions buffer
> I can switch into it, inspect it, ask for defined keys, evaluate with
> M-:, Emacs allows me to remain in the window and go to other
> window. Agenda buffer does not do that, this is probably because it
> just waits for any key and does not allow anything else. That means I
> will open Agenda and I cannot switch to other window, so I will close
> agenda to switch. Maybe I have 10 TODO keywords, I have to open file,
> I open Agenda again, aha, T... then close agenda, open file see
> keyword, then open agenda again. Repetitions without end and user is
> unable to use multiple windows. This really need not be so.
>
> If I open packages' list I can keep the buffer and move to other
> buffer while looking into that list.
>
> You know how agenda is made like the 1985 BASIC menu in Commodore
> C=64, but even back then there was better interface for such menus.