From: pinmacs <pinmacs@cas.cat>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: please, report on current status of orgmode timestamps with timezone
Date: Sun, 8 Dec 2024 17:54:47 +0100 [thread overview]
Message-ID: <7ba7dc55-870c-4ec5-9bfb-b50aded98782@cas.cat> (raw)
In-Reply-To: <87frmye37t.fsf@localhost>
On 2024-12-08 14:03, Ihor Radchenko wrote:
> pinmacs <pinmacs@cas.cat> writes:
>
>>> See https://list.orgmode.org/87tu063ox2.fsf@localhost/ and the parent
>>> thread for details.
>> I am repeatedly seeing this in different places: patches welcome for the
>> new timezone orgmode timestamps. But it points to a thread with 366+
>> messages.
>>
>> I propose to, first off, reduce complexity of the task: Someone should
>> summarize that lengthy conversation with the proposed specification.
> Is the specification provided in
> https://list.orgmode.org/87tu063ox2.fsf@localhost/ (that exact message)
> not clear?
Ah ok, finally! I did not know that on that email contained the
specification. Thank you for clarifying me that.
>> From there, we can move it to a worg page, then, we have a easily to
>> share link to say, this is what we want, patches welcome.
> What do you think we should put on that page?
First of all, it is optional, so take this as "feedback" from user
perspective.
Motivation: I disagree that an email from a mailing list should be the
reference for all orgmode users on the current state of something that
matters (maybe not for everything). When I search on that topic, I got
lost, and that's why I asked on the mailing list. From a user-wide
perspective, it is better if it's a web page (which could source to the
original email).
What information would be on that page? Right now, just the same
information that in that email content from "The proposed new timestamp
syntax" to its end. With a brief introduction saying that this has a
status of a proposal and patches welcome (when this is already done, it
could be a page where people can share recipes on timezones).
This looks better and clearer
https://orgmode.org/worg/timestamp-timezone
Than
https://list.orgmode.org/87tu063ox2.fsf@localhost/
Of course, on my personal basis, I no longer need that because I already
know it, but other people might have that question; or maybe not because
of the additional noise I produced!
And now let me continue with your amazing presentation on emacsconf2024
about the org update situation. And congratulations on stepping up
officially as the new org mantainer
Thanks and health,
pinmacs
prev parent reply other threads:[~2024-12-08 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 2:03 please, report on current status of orgmode timestamps with timezone pinmacs
2024-09-22 17:13 ` Ihor Radchenko
2024-12-08 12:54 ` pinmacs
2024-12-08 13:03 ` Ihor Radchenko
2024-12-08 16:54 ` pinmacs [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=7ba7dc55-870c-4ec5-9bfb-b50aded98782@cas.cat \
--to=pinmacs@cas.cat \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
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).