Leo doesn't write dirty @clean nodes

33 views
Skip to first unread message

p.os...@datec.at

unread,
Mar 17, 2026, 2:54:27 AM (5 days ago) Mar 17
to leo-editor
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

unread,
Mar 18, 2026, 11:32:01 AM (3 days ago) Mar 18
to leo-editor
Thanks for your report. I'll look into this. 
Reply all
Reply to author
Forward
0 new messages