Sylvia van Os

@TheAssassin

I've just reverted 1b4b963bed14fc919141282ced140422929f2f57 and 4120ec76d62f2da74d59b8a4a2db8d5ccc86e3fc, at least restoring the old update check mechanism, so changing this to enhancement for it to use AppImage's mechanism.

There is already an update check for stable releases. Full self-updating would be a much better user experience though.

Sounds like a good idea. Please tell me when it's done. Pext would be happy to be an early adopter :)

Sounds good to me, I'd be happy to :)

I'll probably take a look at it this weekend, thank you :)

https://github.com/Pext/Pext/tree/feature/appimageupdate seems to work...ish. There's just a few weird things. 1. After updating, starting the same AppImage will no longer cause "APPIMAGE" to be in the list of environment variables,...

Regarding 1: I'm not sure if such a hack is a good idea, this seems like something that needs to be looked at in AppImageUpdate itself. Regarding 2: I'm not...

The AppImage created by the Travis build of this branch is still online: https://transfer.sh/gCBAw/Pext-x86_64.AppImage.

I got stuck in a update loop, so I figured I should call the path_to_new_file function. However, that seems to cause a segfault: https://transfer.sh/U8hkG/Pext-x86_64.AppImage (commit: https://github.com/Pext/Pext/commit/ef18d039f4b0fef9f6d10a5038632b0dd656dbd2) ``` Could not find...