From: Daniel Ortmann <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Subject: 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/)]
Date: Wed, 22 Mar 2023 10:53:06 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
* 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
On 3/22/23 10:10, Ihor Radchenko wrote:
> Daniel Ortmann<email@example.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 --]
next prev parent reply other threads:[~2023-03-22 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-03-22 16:06 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).