How are you creating a timestamp? M-x org-schedule? M-x org-deadline? M-x org-time-stamp? Some other way?
If you specify a time with any of the commands above, say Tomorrow at 3pm, it will produce a timestamp that includes a time like <2022-10-08 Sat 15:00>.
Out of curiosity, one thing I couldn’t find is why the value is an alist ("<%Y-%m-%d %a %H:%M>" . "<%Y-%m-%d %a %H:%M>") and not just "<%Y-%m-%d %a %H:%M>", but maybe that’s irrelevant
You’re right, it’s not well documented. The Org codebase uses the first value as the “short” timestamp format (generally used when time is unspecified) and the second as the “long” one. All uses of the variable expect it to be a cons cell, so it cannot be set to a string.
Please don’t do this. It is a constant and you are not supposed to change it. Consequences may be unpredicatable. Instead, just call org-time-stamp with prefix argument.
By typing SPC u (or C-u for non-evil users) before you invoke org-time-stamp. E.g. SPC u M-x org-time-stamp
SPC u / C-u = known as either the universal argument or prefix argument. Is commonly used to indicate to commands you want behavior different from the default. It’s up to the command how they’ll respond to them, but in org-time-stamp's case, it forwards the prefix arg to org-insert-time-stamp, which instructs it to return the long timestamp format.
Unfortunately, this doesn’t work the same way for org-schedule and org-deadline, but giving the calendar prompt a time component (e.g. “tomorrow at 3pm”) gets around that.
Oh, that makes sense, thanks again. I realise that was a really basic question and really appreciate this detailed explanation.
I’ve commented out (setq org-time-stamp-formats '("<%Y-%m-%d %a %H:%M>" . "<%Y-%m-%d %a %H:%M>"))) from config.el and will try to use SPC-u SPC-u SPC-m-d-t instead.
May need to find a way to turn this into a separate function (e.g. org-time-stamp-with-time to avoid so many keystrokes later on.
Strangely enough I had to restart emacs daemon for the change to take effect - I thought that doom/reload would reload changes in config.el. Bearing in mind side effects @yantar92 mentioned I thought that’s a safer way though.