Max Nikulin writes:
> The TZ environment variable is not set and that is the issue. Otherwise
> the .ics file would have
>
> X-WR-TIMEZONE:Europe/London
>
> The problem is that there is no API to get time zone identifier in elisp
> because such function is missed in libc. It is possible to get
On 12/12/2022 21:00, Ihor Radchenko wrote:
Max Nikulin writes:
By default, ox-icalendar takes the value of your TZ environment variable.
I think, in most cases TZ is not set, so (format-time-string "%Z") is
used to get abbreviation (that is ambiguous).
On Linux we may try
timedatectl
Max Nikulin writes:
>> By default, ox-icalendar takes the value of your TZ environment variable.
>
> I think, in most cases TZ is not set, so (format-time-string "%Z") is
> used to get abbreviation (that is ambiguous).
>
> On Linux we may try
>
> timedatectl show --property=Timezone
On 07/12/2022 19:56, Ihor Radchenko wrote:
Neil Jerram:
X-WR-TIMEZONE:BST
which I think was intended to mean British Summer Time; but Google
interpreted it as Bangladesh Standard Time. As a result, my events
from Org are shown at the wrong time in Google calendar.
By default, ox-icalendar
Neil Jerram writes:
> Firstly, when I last exported during late summer, org generated an
> .ics file with
>
> X-WR-TIMEZONE:BST
>
> which I think was intended to mean British Summer Time; but Google
> interpreted it as Bangladesh Standard Time. As a result, my events
> from Org are shown at the
On Wed, 7 Dec 2022 at 11:30, Neil Jerram wrote:
>
> Firstly, when I last exported during late summer, org generated an
> .ics file with
>
> X-WR-TIMEZONE:BST
>
> which I think was intended to mean British Summer Time; but Google
> interpreted it as Bangladesh Standard Time. As a result, my
