From: Yuan Lin <ls.yoyo.m@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: SPC no longer works as a custom agenda key [9.3.4 (9.3.4-elpaplus @ /home/lin/.emacs.d/elpa/26.3/develop/org-plus-contrib-20200206/)]
Date: Mon, 10 Feb 2020 06:27:45 -0500 [thread overview]
Message-ID: <CAP8b++137=x_xvKo3j-iOKO7eSH21UiQD9pbezOU=x+qLzbpYw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
My org-agenda-custom-commands contains
(" " "Notes" tags "NOTE"
((org-agenda-overriding-header "Notes")
(org-tags-match-list-sublevels t)))
notice the key is "SPC" in this case, it used to work without issue. however
after a recent update of spacemacs and package update
(org-plus-contrib-20191230). It suddenly stopped working.
And in the later version I also tried -20200206, it is still broken.
------------------------------------------------------------------------
This issue is initially reported to spacemacs
<https://github.com/syl20bnr/spacemacs> as issue 13138 - SPC no longer
works as a custom agenda command key in org-mode
<https://github.com/syl20bnr/spacemacs/issues/13138>, after some
investigation, it it highly possible that here I quote:
A possible reason why the behavior changed might be because of this commit
from 2 months ago:
https://code.orgmode.org/bzg/org-mode/commit/80b29acba3847c1756fa3c143d6991964f7273ca
agenda: Enable navigation for the agenda dispatch buffer
- lisp/org-agenda.el (org-agenda-get-restriction-and-command): Use
keys C-n, C-p, SPC, DEL analogue to export dispatcher. See function
org-export--dispatch-action.
Reported by Nathan Neff
https://lists.gnu.org/archive/html/emacs-orgmode/2019-10/msg00179.html.
Could those agenda navigation keys made configurable? Or an option to
disable the newly introduced navigation if not needed?
Best Regards,
Yuan
Emacs : GNU Emacs 26.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10)
of 2019-08-29
Package: Org mode version 9.3.4 (9.3.4-elpaplus @
/home/lin/.emacs.d/elpa/26.3/develop/org-plus-contrib-20200206/)
[-- Attachment #2: Type: text/html, Size: 3318 bytes --]
next reply other threads:[~2020-02-10 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 11:27 Yuan Lin [this message]
2020-02-11 0:08 ` Bug: SPC no longer works as a custom agenda key [9.3.4 (9.3.4-elpaplus @ /home/lin/.emacs.d/elpa/26.3/develop/org-plus-contrib-20200206/)] Bastien
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='CAP8b++137=x_xvKo3j-iOKO7eSH21UiQD9pbezOU=x+qLzbpYw@mail.gmail.com' \
--to=ls.yoyo.m@gmail.com \
--cc=emacs-orgmode@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).