You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a D solution with a project that has a symlink folder in its path, the parser won't recognize the project correctly and sets its reference to null in this call:
var document = Ide.IdeApp.Workbench.OpenDocument();
document.Project is null now
Tested on Ubuntu 12.10 (I expect the same behaviour using mklink on Windows).
I just tested enlisting all the files in a directory that contains a symlink under Mint 13..and it also followed symlinks..but wait, you're talking about Projects here..uhm, well, I could imagine that it gets confused when having a document opened that resides in the symlink'd path but you try to open the file via its physical name..well, dunno how to handle this..
If you have a D solution with a project that has a symlink folder in its path, the parser won't recognize the project correctly and sets its reference to null in this call:
var document = Ide.IdeApp.Workbench.OpenDocument();
Tested on Ubuntu 12.10 (I expect the same behaviour using mklink on Windows).
You can find the code in DGdbBacktrace.PrepareParser() method In MonoDevelop.Debugger.Gdb.D project (https://github.com/llucenic/MonoDevelop.Debugger.Gdb.D/blob/master/MonoDevelop.D/DGdbBacktrace.cs#L75)
The text was updated successfully, but these errors were encountered: