I want to correct
my comment about using appimages' portable mode. Truth is, I'd never used that before as I hadn't had the need for it until recently while helping in troubleshooting an appimage which had some problems when opening a folder or file; it crashed every time. The devp published a "RC" with changes to try and fix this, as I didn't want the app to write to my ~/.config folder, I thought of using the portable mode to run the app, I did it by following the official docs' instructions, however, it still did, so I wondered why it didn't work and whether I was missing something, and yeah I was and as you'll see the procedure is actually easier. Also, it seems the documentation is either a bit outdated, or at the very least those instructions are for appimages that have been built with an older appimage toolkit. That all being said, this is what you need to do to be able to use and run appimages in portable mode:
1. Launch a terminal and run the appimage with the flag
--appimage-protable-config which as per the output of
--appimage-help "Creates a portable config folder to use as $XDG_CONFIG_HOME"
Code:
./app_name.AppImage --appimage-portable-config
This will create the
.app_name folder within the same directory the appimage is in.
2. Launch the appimage
Now the appimage will effectively write and save its settings in the folder created in step 1. You can verify that it does by going to that folder and inspecting its contents. Also, this will work once you've integrated the app into your system.
You can also use
--appimage-portable-home which
"Creates a portable home folder to use as $HOME"
Well, that's it. I apologize for my previous mistake and hope that this helps to clarify things up.