Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Gracefully handle non-writeable directory by using a default fallback path #500
When extracting files or creating a new archive, Keka seems to just fail if the current directory is not writable by the user. Using a recent beta version (the one with ACE 2.x support), the app actually just crashed. (I included a crash log from that in the upload for the other ticket, about that beta).
I would suggest that what it should really do is save out to a pre-defined location,
Ideally, Keka would report that it has done this and why, e.g. "
As I noted in the other ticket about the beta with the ACE 2.x stuff in it: when I try to create an archive in a dir without write access, the app just crashes. So, I would not have seen that behavior being added. :-) The logs I linked to include that crash. That archive of logs is toward the (present) end of #402.