emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Ortmann <daniel.ortmann@oracle.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
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 09:49:33 -0500	[thread overview]
Message-ID: <cdf3aca6-ea37-bfc6-9b67-dfdd7a032d86@oracle.com> (raw)
In-Reply-To: <87k00ac6ib.fsf@localhost>

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 !

  reply	other threads:[~2023-03-22 14:51 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   ` Daniel Ortmann [this message]
2023-03-22 15:10     ` [External] : " Ihor Radchenko
2023-03-22 15:53       ` Daniel Ortmann
2023-03-22 16:06         ` Ihor Radchenko

Reply instructions:

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 \
    --in-reply-to=cdf3aca6-ea37-bfc6-9b67-dfdd7a032d86@oracle.com \
    --to=daniel.ortmann@oracle.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


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