* [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/)]
@ 2023-02-21 20:17 Daniel Ortmann
2023-02-22 10:57 ` Ihor Radchenko
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Ortmann @ 2023-02-21 20:17 UTC (permalink / raw)
To: emacs-orgmode
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/)
^ permalink raw reply [flat|nested] 6+ messages in thread
* 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/)]
2023-02-21 20:17 [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
@ 2023-02-22 10:57 ` Ihor Radchenko
2023-03-22 14:49 ` [External] : " Daniel Ortmann
0 siblings, 1 reply; 6+ messages in thread
From: Ihor Radchenko @ 2023-02-22 10:57 UTC (permalink / raw)
To: Daniel Ortmann; +Cc: emacs-orgmode
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>
^ permalink raw reply [flat|nested] 6+ messages in thread
* 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/)]
2023-02-22 10:57 ` Ihor Radchenko
@ 2023-03-22 14:49 ` Daniel Ortmann
2023-03-22 15:10 ` Ihor Radchenko
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Ortmann @ 2023-03-22 14:49 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: emacs-orgmode
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 !
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* 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/)]
2023-03-22 14:49 ` [External] : " Daniel Ortmann
@ 2023-03-22 15:10 ` Ihor Radchenko
2023-03-22 15:53 ` Daniel Ortmann
0 siblings, 1 reply; 6+ messages in thread
From: Ihor Radchenko @ 2023-03-22 15:10 UTC (permalink / raw)
To: Daniel Ortmann; +Cc: emacs-orgmode
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>
^ permalink raw reply [flat|nested] 6+ messages in thread
* 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/)]
2023-03-22 15:10 ` Ihor Radchenko
@ 2023-03-22 15:53 ` Daniel Ortmann
2023-03-22 16:06 ` Ihor Radchenko
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Ortmann @ 2023-03-22 15:53 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: emacs-orgmode
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-03-22 16:05 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-02-21 20:17 [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
2023-02-22 10:57 ` Ihor Radchenko
2023-03-22 14:49 ` [External] : " Daniel Ortmann
2023-03-22 15:10 ` Ihor Radchenko
2023-03-22 15:53 ` Daniel Ortmann
2023-03-22 16:06 ` Ihor Radchenko
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).