Updating Generic Linux Releases What Files to Overwrite

[Random Void User]

Using generic Linux releases (*.tar.xz) to update CudaText, obviously the main app (ELF) must overwrite the old app. No instructions say what other new files should overwrite old ones. Is it sufficient to run the new binary and update all plugins via Addons Manager? Thanks.

[main Alexey]

wiki:
>>.xz package. It is intended that user just unpacks this archive, to subdirectory of home-directory, and then runs binary "cudatext" from there. This is simpler way. But additional way is also possible - you can "install" the program, so that "cudatext" will be runnable from Terminal. The "installation" is:

you should overwrite all files from .xz package.

[Random Void User]

I already use a special folder for CudaText on $PATH. So I can run from terminal if desired. But I also use a .desktop file for the windowing system. I need --disableaccurateframe, which is a hassle, but easy to put in the .desktop file.

All files but the binary app inhabit $XDG_CONFIG_HOME/cudatext. I wish CudaText would first check the location from which it is run for plugins and settings. Then it would become a proper "portable app" without needing the -s command line switch.

Does -s cause CudaText to load all plugins from the designated location, not just user settings? Can I delete $XDG_CONFIG_HOME/cudatext if I use -s? Note, one should not put binary apps in $XDG_CONFIG_HOME, and $XDG_CONFIG_HOME should not be on $PATH.

I have all plugins installed. When I update a new CudaText release, I run the Addons Manager to update anything new. Is that procedure correct?

Thanks for the rapid releases! So far I love CudaText and use it daily.

[main Alexey]

> I wish CudaText would first check the location from which it is run for plugins and settings. Then it would become a proper "portable app"

something like this is already implemented.
quote from wiki: CudaText distributions are portable, if the executable file is located near the "data" sub-folder. So the distribution for Windows is portable (executable "cudatext.exe" is located near "data"), and distributions from .xz archives are portable too.

>Does -s cause CudaText to load all plugins from the designated location, not just user settings?

no. plugins live in 'py' folder (usually near 'data') and it's not related to 'settings'.

>Can I delete $XDG_CONFIG_HOME/cudatext if I use -s?

seems yes, you can try it.

> I run the Addons Manager to update anything new. Is that procedure correct?

yes, it is.

[Random Void User]

Everything works! No more $XDG_CONFIG_HOME/cudatext. I had no problems at all. CudaText is now "portable" on my system, practically as good as an AppImage.