Leo doesn't write dirty @clean nodes

[p.os...@datec.at]

I'd like to use Leo to maintain 2 projects, that share some code. My idea was to have C-files with a node for code concerning the one file (e.g. file_1.c XOR file_2.c) and a clone node for common  code. Now, when I change code in file_2.c in an IDE being the common part, Leo reads file_2.c and writes them to disk on "Save" as expected. I'd expected, too, that file_1.c is written as well, but isn't. 

How do you overcome that? Or should I follow a different strategy?

BTW: I use @clean-nodes because they work w/o sentinels.

Cheers
Paul

[Félix]

Thanks for your report. I'll look into this. 

[Edward K. Ream]

On Wed, Mar 18, 2026 at 10:32 AM Félix <felix...@gmail.com> wrote:

Many thanks for this report. I do see the (subtle) behavior you report. 

I have just created #4565 for this.

Edward

[p.os...@datec.at]

Installed 6.8.8 minutes ago and it works. Many thanks. A detail though: The log window reads when saving:

wrote: file_1.txt
unchanged: file_2.txt
finished: 1 unchanged file

As both files were written, I think it should read:

wrote: file_1.txt
wrote: file_2.txt
finished: 1 unchanged file

Paul