As I told you, a batch file or yaP launcher are ways to solve many portability issues -- I'll introduce one way to solve that last hurdle bellow. But first, let me sum up your findings so we are on the same page here.
If I understand it correctly, creating a 'data' sub-folder in the program folder and moving 'ghostwriter.ini' there (BTW, you didn't try creating an empty one there, did you?) keeps vs-ghostwriter from writing settings to 'appData/roaming' but not from leaving some traces in 'appData/local', right?
If you use the following code as a yaP launcher configuration, those traces will expectably be moved back and forth upon program execution.
Code: Select all
; configuration file for yaP v0.7.1.5 (http://rolandtoth.hu/yaP/) ; application name: vs-ghostwriter ; version: v1.8.0 ; website: https://github.com/michelolvera/vs-ghostwriter [GENERAL] application = App\ghostwriter.exe ; commandline = ; workdir = [BEFORE] dir = %APPDATA%\ghostwriter ...
I might be able to test this later, but I'll just leave it here for the time being.