Ihor Radchenko <yanta...@gmail.com> writes:
> Arthur Miller <arthur.mil...@live.com> writes: > >> this example the mode map approach seems slightly more convenient. I don't >> know, >> in org-agenda-test, I haven't implemented all of org-agenda, restrictions, >> prefixes and some other stuff, mostly because I don't really understand the >> implementation. > > In the nutshell, agenda restrictions will execute some elisp that sets > certain global variables affecting other agenda commands. selecting the > restriction should not leave the agenda menu. > > Also, unlike other selections being echoed literally upon selection, > restriction echo must depend on the global state. If you press "<" in > the menu, the menu prompt should change between "Press key for agenda > command (unrestricted):", Press key for agenda command (restricted to > buffer):, ... etc > > Note that there is not much point echoing the selection. > Tim, do I understand correctly that changed minibuffer prompt will be > also spoken out by emacspeak? > I think so, but this would need to be verified. A lot depends on how/where Emacs does things - for example, because Emacspeak relies on the advice mechanism, it cannot pickup changes/actions which occur in pure C code. Provided Emacspeak is able to get the prompt in some before, after or around advice call, all should be fine.