From: Robert Pluim <rpluim@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] org.el (org-read-date): Point to Info documentation
Date: Tue, 21 Jun 2022 11:43:31 +0200 [thread overview]
Message-ID: <877d5axsfw.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
I was just about to start implementing calendar navigation commands
for org-read-date, except that they all already exist :-). Theyʼre
just not documented in the docstring, only in the manual. Patch
adding a cross-reference attached.
Robert
--
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org.el-org-read-date-Point-to-Info-documentation.patch --]
[-- Type: text/x-diff, Size: 1082 bytes --]
From bded6dfd8d6340d8330f8c1f11a46a140082f3b5 Mon Sep 17 00:00:00 2001
From: Robert Pluim <rpluim@gmail.com>
Date: Tue, 21 Jun 2022 11:36:24 +0200
Subject: [PATCH] org.el (org-read-date): Point to Info documentation
* lisp/org.el (org-read-date): Add reference to Info documentation,
mainly because that describes all the available calendar navigation
commands.
---
lisp/org.el | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lisp/org.el b/lisp/org.el
index 5b034ae12..c1fb8df4f 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -13327,6 +13327,9 @@ (defun org-read-date (&optional with-time to-time from-string prompt
While prompting, a calendar is popped up - you can also select the
date with the mouse (button 1). The calendar shows a period of three
months. To scroll it to other months, use the keys `>' and `<'.
+There are many other calendar navigation commands available, see
+Info node `(org) The date/time prompt' for a full list.
+
If you don't like the calendar, turn it off with
(setq org-read-date-popup-calendar nil)
--
2.35.1.607.gf01e51a7cf
next reply other threads:[~2022-06-21 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 9:43 Robert Pluim [this message]
2022-06-23 13:28 ` [PATCH] org.el (org-read-date): Point to Info documentation Ihor Radchenko
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=877d5axsfw.fsf@gmail.com \
--to=rpluim@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).