[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: org-read-date-minibuffer-local-map should use C-n/p/f/b
From: |
Bastien |
Subject: |
Re: org-read-date-minibuffer-local-map should use C-n/p/f/b |
Date: |
Fri, 04 Sep 2020 18:18:14 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
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.
Thanks,
--
Bastien
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: org-read-date-minibuffer-local-map should use C-n/p/f/b,
Bastien <=