plasma-applet-eventcalendar VS client

Problem reporting

v76 = https://github.com/Zren/plasma-applet-eventcalendar/releases/tag/v76

Also, practically every KDE rice with a clock uses Event Calendar instead of the default clock. It's extremely customizable in how it displays the time.

Check out Event Calendar widget. It has a ton of options over the default clock widget and I believe it's possible to load up a calendar without relying on akonadi or kdepim and get notifications for it that way.

If you're looking for an alternative calendar that can do this, check out Zren's Event Calendar.

I have this widget that basically replaced both kalendar and korganizer with: https://store.kde.org/p/998901

Well, owncloud run into similar issues with their client before the functionality was rolled into Qt and it mentions APFS as well as non-utf8 linux locals so... https://github.com/owncloud/client/issues/5650 https://github.com/owncloud/client/pull/5875

Why is koofr not able to get a working sync application whereas ownloud has one that works perfectly since ages? And it is even open source, so koofr devs can look and see what they are doing wrong! https://github.com/owncloud/client

There was a delta sync implementation based on zsync that got merged in the master branch of oc10, and the $1,755k bounty was paid, see Welcome Delta Sync for ownCloud - ownCloud, the client issue, one of the central client PRs , the server side PR ... sadly that feature never made it through QA. And it crashed the client .

https://github.com/owncloud/client/issues/567#issue-13530273

I agree with you guys that systemd would be better suited for this job than cron. That being said, I didn't create this tool. I simply tried it out, saw that it solved my problem, and decided to add it to the AUR. This was more of an AUR learning exercise than anything. Ideally, nextcloud implements a proper sync client daemon as requested in https://github.com/owncloud/client/issues/2002. Then there would be no need for any of this hackery!