https://bugs.kde.org/show_bug.cgi?id=384185
--- Comment #4 from Oliver Sander ---
No, I merely looked at these patches, but never tested them.
More experimentation has revealed the following: Automatic reload does work as
expected when I 'touch' the file, or when I save it from 'vi'. It does no
https://bugs.kde.org/show_bug.cgi?id=384185
Julian Wolff changed:
What|Removed |Added
CC||wo...@julianwolff.de
--- Comment #5 from Julian
https://bugs.kde.org/show_bug.cgi?id=384185
--- Comment #6 from Albert Astals Cid ---
We had code for this, i guess someone broke it when porting to KF5.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=384185
--- Comment #7 from Albert Astals Cid ---
After reading the code i agree it seems a regression in kdirwatch
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=384185
--- Comment #8 from Albert Astals Cid ---
Meh, it's probably a regression in inotify since i build the old kdelibs4
version and that doesn't work anymore either. I'll try to add some more code
and ideally an autotest.
--
You are receiving this mail be
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/130235/#review103678
---
> How do I make it go into effect when 'Ok' is clicked? I s
aacid added a comment.
Is it possible that a memory leak sneaked in in this code?
Without this code if i run
./autotests/editannotationcontentstest
i don't get any memory leak but with it i get
5: Direct leak of 131076 byte(s) in 4 object(s) allocated from:
5: #0 0x7
