[BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

[BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

[Daniel Ortmann]

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.
------------------------------------------------------------------------

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.

Emacs : GNU Emacs 30.0.50 (build 10, x86_64-pc-linux-gnu, GTK+ Version 
3.22.30, cairo version 1.15.12)
of 2023-02-21
Package: Org mode version 9.6.1 (release_9.6.1-262-gd94f40 @ 
/home/dortmann/src/git-org-mode/lisp/)

Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

[Ihor Radchenko]

Daniel Ortmann <daniel.ortmann@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 ! 

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

[Daniel Ortmann]

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.ortmann@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 !
>

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

[Ihor Radchenko]

Daniel Ortmann <daniel.ortmann@oracle.com> 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.)

May you elaborate? Are you sure that you are replying to the right thread?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

[Daniel Ortmann]

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

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 1970.


(Yes, I am replying to the correct thread which corresponds to the bug 
report submitted.)

On 3/22/23 10:10, Ihor Radchenko wrote:
> Daniel Ortmann<daniel.ortmann@oracle.com>  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.)
> May you elaborate? Are you sure that you are replying to the right thread?
>

[-- Attachment #2: Type: text/html, Size: 1537 bytes --]

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

[Ihor Radchenko]

Daniel Ortmann <daniel.ortmann@oracle.com> 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] as the default date and 
> not change that date to 1970.

See https://orgmode.org/list/87v8itnh20.fsf@localhost
You can just set `org-read-date-force-compatible-dates' to nil.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>