Arch Linux User Repository

Yes please! I haven't thought about this before but I like that. Resource usage is one of the main problems of electron-based applications.

Is there any advantage over official todist-appimage and todoist-electron which was officially recommended before?

The main advantage is the shared runtime, which hopefully saves some RAM and CPU cycles, at the expense of a slightly higher chance of breaking between major releases of Electron (unlikely, since, AFAIK, Electron never introduces breaking changes without putting them behind a flag first and asking everybody to adjust their code). Todoist's official app doesn't appear to do anything special, so there's no sacrifice.

Speaking of, do you mind if I switch this package to the same style of PKGBUILD as todoist-nativefier, i.e. use shared Electron?

Alright thank you. I'll be co-maintaining to stay up to date until the other packages are adopted.

Offtopic: I switched away from google services, therefore i'm using a nextcloud calendar and and todoist for notes. I see you're maintaining todoist-nativefier, cool! Is there any advantage over official todist-appimage and todoist-electron which was officially recommended before ?

I maintain other Nativefier-based packages, so happy to adopt this one, but not the other two, sorry. Off-topic, but what do you use instead, if not a secret?

Thank you for the heads up, that is quite annoying. Especially as i don't use it myself anymore and therefore cannot see it within short time to update again. If somebody would like to adopt this one, that one and the other one I'd be happy to hand over responsibilities.

Please, consider bumping the pkgrel every 59 days, because otherwise every user of this package needs to rebuild it manually, as to avoid the old build warning, which starts coming up for builds which are 60+ days old. The warning can be disabled, but this is a good practice regardless.

Please, consider bumping the pkgrel every 59 days, because otherwise every user of this package needs to rebuild it manually, as to avoid the old build warning, which starts coming up for builds which are 60+ days old. The warning can be disabled, but this is a good practice regardless.

Hello, there was a nativefier update today that probably broke the name scheme.

Quickest fix is restoring the previous version of nodejs-nativefier. I'll update this package later to match the nativefier update

EDIT: Hello, i could build the PKGBUILD file just fine. Which AUR helper did you use? Can you post the complete build log to pastebin or similar?

EDIT2: Try again with the new package

Hello,

I get the following error while building:

cp: cannot stat 'google-calendar-linux-*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

Any quick fix for this? :)

Cheerio!

Updated the application:

changes:

• fixed build process for new nativefier version

• fixed google login by using a firefox user agent

• use electron 7.1.11 instead of the default nativefier 5.x version to fix re-login on every restart

The Google login process with electron is a little tricky, sometimes it gives "cookies disabled" errors, then just try again...