Since that existing timestamp at point is supposed to be used as the
default, we definitely have a bug
==>> ... Since that 'default' time is bumped up to 1970.
Clearly, the expected default behavior is not working as expected.
(Times after 1970 are fine.)
On 2/22/23 04:57, Ihor Radchenko wrote:
Daniel Ortmann <daniel.ortm...@oracle.com> writes:
file org-plain-date-to-date-time.org has:
* plain date
C-c ! gives:
[2023-02-21 Tue]
* updating plain date
C-c ! followed by C-u C-! gives:
[2023-02-21 Tue 00:00]
* date-time
C-u C-c ! gives:
[2023-02-21 Tue 14:13]
I expected that updating an existing date with C-u C-c ! would produce
the same result as creating a new date-time.
When point is at existing timestamp, C-c ! tries to take the time of
that timestamp as default. To force today's date and time, you can use
C-u C-u C-c !
