https://bugs.kde.org/show_bug.cgi?id=387391
--- Comment #9 from Venca B Spam <vbs...@centrum.cz> ---
Yes, I guess that it may be the issue. If the state machine (whatever logic)
expects the state has some meaning and it behaves a bit different it may have
unpredictable results.
In fact the symlink os API sometimes resolve symlinks sometimes do not. Symlink
itself is just inode pointing to another inode. Depends on how you watch files,
it may return results which may not be understandable for the parser.
I can imagine following:
string watch_inode_file( string file) {..}
when called:
auto result = watch_inode_file( "/path/to/project/symlinked_dir/file.cpp");
may return in result="/path/somewhere/else/symlinked_dir/file.cpp".
--
You are receiving this mail because:
You are watching all bug changes.
