> On 2022-09-09, at 9:18 AM, David T. Lewis <lewis at mail.msen.com> wrote:
> 
> On Thu, Sep 08, 2022 at 10:08:00PM -0500, Chris Muller wrote:
>> 
>> On Thu, Sep 8, 2022 at 2:33 PM Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
>>> 
>>> probably a simple FAQ, but I did not find a simple answer to it: What
>>> would be the easiest way to clear my changes file? The background is
>>> that I have a "fresh trunk image" which I open several times a day to
>>> test anything out, make some changes to some classes, or install several
>>> Metacello packages but eventually close the image without saving. This
>>> bloats my changes file. How can I empty it again and remove all old
>>> do-its, prior method versions, and so on? The "remove" items in the
>>> change list tool do not seem to have any effect for me.
>>> 
>> 
>> I solve this with "Save as...".  First thing from the stock trunk
>> image is to "save as" your work name.  Then, within that work, the
>> same thing -- save as "_temp", do the load, then, if everything is
>> good, save back as the original work name.  If not, you have the old
>> work image and unbloated changes.
>> 
> 
> That's what I do also.
> 
> Another simple way approach is to keep your stock trunk image and
> changes files in a zip or tgz archive, and unzip them when you are
> ready to start fresh.

This is why I think we should make the default image read-only, and insist on that image being saved under a new name/location as the very first thing. I.e. treat the default image in the way that many applications treat templates.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Change is inevitable....except from vending machines.