emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Matthew Lundin <mdl@imapmail.org>
Cc: Alex Branham <alex.branham@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-read-date-minibuffer-local-map should use C-n/p/f/b
Date: Fri, 04 Sep 2020 18:18:14 +0200	[thread overview]
Message-ID: <87h7sdh5x5.fsf@gnu.org> (raw)
In-Reply-To: <87tuzyf8hc.fsf@fastmail.fm> (Matthew Lundin's message of "Fri, 29 May 2020 21:43:27 -0500")

Hi Alex and Matthew,

Matthew Lundin <mdl@imapmail.org> writes:

> Alex Branham <alex.branham@gmail.com> writes:
>> I find it unintuitive that the usual calendar keys C-n/p/f/b don't work
>> when scheduling tasks in org mode (yes, I know about S-right, etc). I've
>> something like this to my init file for those four keys (based on their
>> setup in org-keys.el) for some time with no negative repercussions (that
>> I know about anyway), perhaps the same should be done for org itself?
>> #+begin_src emacs-lisp
>> (define-key org-read-date-minibuffer-local-map (kbd "C-n") (lambda
>> () (interactive) (org-eval-in-calendar '(calendar-forward-week 1))))
>> #+end_src
> While I can't think of any obvious conflicts for C-n and C-p in the
> context of the read date minibuffer (please correct me if I'm wrong),
> C-f and C-b are bound to forward-char and backward-char, which I
> frequently use when entering and editing dates.

I agree with Matt on this: I also use C-f and C-b here, and adding
C-n and C-p only makes sense if we add all four keys.  So I suggest
not to add these keybindings.



      reply	other threads:[~2020-09-04 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 16:59 org-read-date-minibuffer-local-map should use C-n/p/f/b Alex Branham
2020-05-30  2:43 ` Matthew Lundin
2020-09-04 16:18   ` Bastien [this message]

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:

  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=87h7sdh5x5.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=alex.branham@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \


* 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


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).