Caught it again. The complete scenario:
- small html file with @others
- one of the @other is for css
- tweaking one of the value, this looks like 'write a couple of symbols,
save, ctrl-z, save, ...'
after one of the ctrl-z the changes were not saved.


пн, 9 дек. 2019 г. в 16:58, gar <[email protected]>:

> Hello. Was away for weekend.
> Starting to use the branch. Let's observe for some days...
>
> сб, 7 дек. 2019 г. в 16:35, Edward K. Ream <[email protected]>:
>
>> For those troubled by this bug, please check out the "bug-1451" branch
>> and run Leo with --trace=save enabled.  This will tell you (in the console)
>> what at.findFilesToWrite thinks should be written, and why.
>>
>> Please let me know what, if anything, you see when Leo fails to write an
>> @clean file as expected.
>>
>> Edward
>>
>> P. S. I can't duplicate this bug.  I have taken a close look at all the
>> code and can find nothing amiss re #1451
>> <https://github.com/leo-editor/leo-editor/issues/1451>.  This proves
>> nothing ;-)
>>
>> Clearly, something strange is going on. It's particularly strange that
>> using @nosent should work when @clean doesn't, because exactly the same
>> write code is used for both!
>>
>> EKR
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "leo-editor" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/leo-editor/9f540b14-1177-4d63-ae04-6781ba0f2440%40googlegroups.com
>> <https://groups.google.com/d/msgid/leo-editor/9f540b14-1177-4d63-ae04-6781ba0f2440%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVxKD7i8Va4-sobc%3DH8AKJ5HzRs_KuLOdwwAY5_GUekPgA%40mail.gmail.com.

Reply via email to