It appears that tym.get_config_path() does not work when I state --use explicitly about tym HOT 4 CLOSED

Thanks again! I fixed that. Maybe ok.

from tym.

Why "maybe"? everything is working perfectly now! :-)
I had forgotten to report that opening more than one tym instances, closing one would close all of them before, sort of crashing.
Now it doesn't happen anymore and I can create different profiles anywhere, even outside of XDG_CONFIG_HOME.
What I was trying to achieve without succeeding is perfectly workable now.
I have repeated my tests several times and, in addition, the warning messages in the logs that I used to see before have also disappeared now.
As far as I am concerned I would already close the issue now but since you are apparently left in doubt, do it yourself as soon as it seems appropriate to you :)

from tym.

Because I wrote the fix with my drunk brain, haha...

By default, tym's all instances(windows) are spawned from the single primary process. So, if tym encounters a fatal error, the process goes down and all instances will be collapsed.

The error of this issue may have been the reason why "closing one would close all of them before, sort of crashing." .

The --isolated option make tym spawn a new process by each instance and would avoid "chained destruction" when this kind of problem occurs.

from tym.

Yes yes, it is clear to me now and I had also observed it via the task manager with which I visually observed the birth of a new process by declaring --isolated.
Enjoy your good and well-deserved drink!!! ;-)

from tym.