Daniel Ortmann writes:
> Ihor,
>
> * In an org buffer, input: [1960-10-16]
> * Set point between the brackets.
> * Press C-c ! and enter.
> * The result is [19_*7*_0-10-16 Fri]
> * I expected [1060-10-16-Sun]
>
> Yes, C-c C-c works.
>
> But C-c ! enter is supposed to use [1960-10-16]
Ihor,
* In an org buffer, input: [1960-10-16]
* Set point between the brackets.
* Press C-c ! and enter.
* The result is [19_*7*_0-10-16 Fri]
* I expected [1060-10-16-Sun]
Yes, C-c C-c works.
But C-c ! enter is supposed to use [1960-10-16] as the default date and
not change that date to
Daniel Ortmann writes:
> 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.)
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
Daniel Ortmann 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
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
