From: Ihor Radchenko <yantar92@posteo.net>
To: "Stephen J. Eglen" <sje30@cam.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Jan Tatarik <jan.tatarik@gmail.com>
Subject: Re: help with gnus-icalendar.el and orgmode agenda
Date: Wed, 07 Feb 2024 22:55:41 +0000 [thread overview]
Message-ID: <874jejrij6.fsf@localhost> (raw)
In-Reply-To: <m2ttmkxai0.fsf@cam.ac.uk>
"Stephen J. Eglen" <sje30@cam.ac.uk> writes:
> When I use this package on icalendar attachments, it creates entries
> that look like this:
>
> ...
> <2024-02-22 18:30-20:00>
>
> Note that the timestamp DOES NOT include a day of the week. With the
> default settings of org-time-stamp-formats, i.e.
>
> ("%Y-%m-%d %a" . "%Y-%m-%d %a %H:%M")
>
> this means that the agenda does not show this entry -- which defeats the
> purpose of me saving the icalendar entry! If I manually add the dayname
> then the agenda item appears.
<2024-02-22 18:30-20:00> is a valid timestamp. Agenda not handling it is
an oversight that should be fixed.
That said...
> (format "<%s %s-%s%s>" start-date start-time end-time repeat)
>
> which does not include the dayname.
could certainly be improved. Having a day name increases readability.
Also, we may change the format in future, adding time zones as well.
I recommend using `org-time-stamp-format' when creating Org mode
timestamps or even `org-element-timestamp-interpreter'.
--
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>
next prev parent reply other threads:[~2024-02-07 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 20:41 help with gnus-icalendar.el and orgmode agenda Stephen J. Eglen
2024-02-07 22:55 ` Ihor Radchenko [this message]
2024-02-07 23:20 ` Stephen J. Eglen
2024-02-08 15:03 ` 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:
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=874jejrij6.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jan.tatarik@gmail.com \
--cc=sje30@cam.ac.uk \
/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).