Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renaming .appimage.home and .appimage.config with update #171

Open
adnan360 opened this issue Apr 10, 2021 · 1 comment
Open

Renaming .appimage.home and .appimage.config with update #171

adnan360 opened this issue Apr 10, 2021 · 1 comment

Comments

@adnan360
Copy link

Background:

When I use an appimage, I usually keep a <appimage filename>.home and <appimage filename>.config directory beside it so that files created by that appimage doesn't get into my user home directory and they're more controllable this way. This works for me so well and it has worked for every appimage I tried so far.

e.g.

before update

When the update completes, the new file is created, but the directories have the same name as before.

after update

Steps to reproduce:

  • Download an old appimage (for example this one)
  • Create directories named <appimage filename>.home and <appimage filename>.config beside it
  • Launch AppimageUpdate and show the appimage so that it can update

Current behavior:

Keeps the .home and .config directory names as is, does not update the names according to the new version updated.

Expected behavior:

Rename the .home and .config directories to reflect the latest version downloaded. If it is too direct, maybe a Yes-No message box can ask if the names should be updated.

@probonopd
Copy link
Member

Rename the .home and .config directories to reflect the latest version downloaded. If it is too direct, maybe a Yes-No message box can ask if the names should be updated.

Some users like to keep these directories per-version, so that the settings of a newer application version don't change/damage the settings of the older application version.

I think it is reasonable for the user to rename them if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants