From: Tim Ruffing <crypto@timruffing.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Date prompt suggests yesterday when changing timestamp with org-extend-today-until set [9.6]
Date: Fri, 10 Mar 2023 00:26:23 +0100 [thread overview]
Message-ID: <c37b1e4653dae395f14ef1af7f23b37a20128a0a.camel@timruffing.de> (raw)
In-Reply-To: <87zgaan68a.fsf@localhost>
Sorry for the late reply. The patch solves the problem for me, thanks!
Would be great to have this fixed.
On Sun, 2023-01-22 at 11:44 +0000, Ihor Radchenko wrote:
> * This is test
> SCHEDULED: <2023-01-28 Sat>
>
> Then, M-: (setq org-extend-today-until 20)
> Then, C-c C-s on the heading above
>
> What will happen if one tries to do "." or +1 or ++1. I find the
> current
> behavior rather disorienting. Could someone check what we promise in
> the
> Org manual, `org-read-date' docstring, `org-extend-today-until'
> docstring, and what actually happens in practice?
>
Unless you see a bug that I'm not seeing, the behavior looks correct to
me (with the patch applied): The default date (when the user hasn't
entered anything) is the existing timestamp. Then "." selects today
explicitly, "+" is relative to today, and "++" is relative to the
default date. That's exactly what's promised
in https://orgmode.org/manual/The-date_002ftime-prompt.html and also in
the `org-read-date` doctring. (And I think it makes sense.)
Best,
Tim
next prev parent reply other threads:[~2023-03-09 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 11:55 [BUG] Date prompt suggests yesterday when changing timestamp with org-extend-today-until set [9.6] Tim Ruffing
2023-01-22 11:44 ` Ihor Radchenko
2023-03-09 23:26 ` Tim Ruffing [this message]
2023-03-11 9:33 ` 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=c37b1e4653dae395f14ef1af7f23b37a20128a0a.camel@timruffing.de \
--to=crypto@timruffing.de \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).