[Cuis-dev] user.changes files

[Alexandre Rousseau]

A functional workflow with safe (from loss), sharable outcomes (packages)
has been on my mind these past few days. That, plus the fact that I lost a
whole category of work this morning makes this even more important. Your
notes help a lot. Thanks!

On Sun., Mar. 26, 2023, 10:19 a.m. Bernhard Pieber via Cuis-dev, <
cuis-dev at lists.cuis.st> wrote:

> Hi everyone,
>
> I just read up on the purpose of the user.changes file because I had not
> understood them properly. In case others are wondering as well I found
> these mails most informative:
>
> Thread New User Changes log file
>
> http://cuis-smalltalk.org/pipermail/cuis-dev_cuis-smalltalk.org/2018-July/003755.html
>
> Thread Changes not recoverable
> https://lists.cuis.st/mailman/archives/cuis-dev/2020-December/002545.html
> https://lists.cuis.st/mailman/archives/cuis-dev/2020-December/002552.html
> https://lists.cuis.st/mailman/archives/cuis-dev/2020-December/002556.html
>
> I learned that code that you file in only goes to the changes file. Manual
> code changes and do-its are written to the .user.changes file and the
> .changes file. This makes recovery easier. However, in case you don’t save
> your image all changes since the last image save remain only in the
> user.changes file. So the user.changes file are not totally redundant. If
> you just delete all of them, you might not be able to recover all code
> changes you did.
>
> If the amount of user.changes file bothers you you can use the Preference
> #autoNumberUserChanges to have just one.
>
> If I read the code correctly if file-in fails user changes might stop to
> be written. The attached change set should fix that.
>
> Cheers,
> Bernhard
>
> --
> Cuis-dev mailing list
> Cuis-dev at lists.cuis.st
> https://lists.cuis.st/mailman/listinfo/cuis-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20230326/ac3481c7/attachment-0001.htm>