Lars Henriksen

> Sure. We need to make sure we don't sacrifice too much of the simplicity of the data file format, though. So how exactly do you suggest to extend the...

RFC5545 explicitly defines that the rule parts are not ordered in any particular sequence in the iCalendar data format. But I so no reason why the calcurse file format should...

> [test.ics.txt](https://github.com/lfos/calcurse/files/5453140/test.ics.txt) > [calcurse_log.WXqMzB.log](https://github.com/lfos/calcurse/files/5453141/calcurse_log.WXqMzB.log) Thank you for this report from the real cyber world. I will give some comments on the test file. Numbers in parenthesis refer to section numbers...

> I have the same issue that @mvhulten described. Maybe he messed up his "minimal failing example" here, but the issue persists. I will assume that @mvhulten provided a valid...

> Thankfully calcurse ignores the TZID. AFAIK "W. Europe Standard Time" is what Britain and Portugal have, However the time zone info like TZOFFSET shows the central European time zone....

Ubiquitous? At least on Unix-like systems, presumably including MAC OS X. That makes the time zone component in your test file even stranger. An iCalendar time zone component is meant...

> When import fails, like in this case, `calcurse -i` returns an error code of `0`, so it's not easy to catch the error in a script. @mvhulten, should calcurse...

> ... but it seems one cannot run multiple instances at the same time, so that's a pain. Is this the case, or am I missing something? You are. See...

What you want is not possible at present. The notification system in `calcurse` is very limited and probably not what you expect. For an explanation see https://github.com/lfos/calcurse/issues/285#issuecomment-620841221. Aside: version 4.3.0...

> **Reproduce.** E.g., with https://paste.debian.net/hidden/55688842/, I get told on every startup that this and that key had been assigned to this and that action as per some default, but that...