"Fresh" isn't necessarily so. Should it be?

[Malarki]

Sort of a wish... unless something's wrong with my usage or understanding or installation, which is often the case.

Apparently, when I open a "::fresh" instance of XY, it will actually use whatever was in the "Fresh" folder before. It doesn't start from scratch. I only noticed this today when testing a script, and was surprised to find other versions of it from months ago in the (Fresh) Scripts folder.

So maybe XY should empty the Fresh folder when that instance is closed.

[admin]

Can't reproduce. Which setting for example is not fresh?

[Malarki]

Not an XY setting, but stuff in the Fresh Data folders such as scripts. That remains after a Fresh instance is killed.

Maybe the "Fresh" concept is only meant to apply XY settings. It's just surprising to find old scripts, for example, when navigating to the Script folder in a Fresh instance.

So, a design / intent decision. I looked but didn't find that the topic had come before.

[admin]

Yes, a design decision. I may not have talked about it much. The point is that the fresh version is mostly for debugging, and it can come in handy to have some things ready to try, so I decided not to wipe everything away when exiting fresh.