Editing a symlinked file in codeblocks removes the symlink and saves a new file with the same name and new content.
I think this behaviour is wrong, not expected or at least there should be an option to disable it.
This happens on Linux, I don't know what happens with symlinks on Windows.
Note oBFusCATed: The proper way is to detect that the file is a link and then disable the temp+move mechanism we're using.
Additioal note: This has to work on all pltforms reliable. Remember that on Windows you can have soft/hardlinks, too (softlinks might be something to ignore because it would not work with the compiler anyways).
Is it of concern to handle the case where a (malicious) program swaps/changes target for the symlink just before C::B saves to it?
I don't think so.
Fixed in [r11008]
Related
Commit: [r11008]
@Alpha: Can you update the comment before/in the function to describe what is going on?
Done in [r11013]
Related
Commit: [r11013]