* org-read-date-minibuffer-local-map should use C-n/p/f/b
@ 2020-05-29 16:59 Alex Branham
2020-05-30 2:43 ` Matthew Lundin
0 siblings, 1 reply; 3+ messages in thread
From: Alex Branham @ 2020-05-29 16:59 UTC (permalink / raw)
To: emacs-orgmode
Hello -
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
Thanks,
Alex
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: org-read-date-minibuffer-local-map should use C-n/p/f/b
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
0 siblings, 1 reply; 3+ messages in thread
From: Matthew Lundin @ 2020-05-30 2:43 UTC (permalink / raw)
To: Alex Branham, emacs-orgmode
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.
Best,
Matt
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: org-read-date-minibuffer-local-map should use C-n/p/f/b
2020-05-30 2:43 ` Matthew Lundin
@ 2020-09-04 16:18 ` Bastien
0 siblings, 0 replies; 3+ messages in thread
From: Bastien @ 2020-09-04 16:18 UTC (permalink / raw)
To: Matthew Lundin; +Cc: Alex Branham, emacs-orgmode
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-09-04 16:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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).