Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
monodevelop/main/src/core/Mono.Texteditor/Mono.TextEditor/Document/TextDocument.cs line 1700 is not implemented right, because it simply ignores the anchor.
Fix this please.
That's just for compatibility with the NRefactory interface.
We don't support the anchor type, nor do I plan to do so. That's SharpDevelop specfic.
They use this option to have more control how the caret and certain anchors move - I don't see any use case for refactoring commands using that.
Ok that method was part of the public API - that wasn't intended. It now explicitly implements the IDocument interface.
- again only needed as NRefactory bridge.
but why don't you implement that? I mean, it is that difficult? I don't think so. E.g. the MagicKeyCompletion (main/contrib/ICSharpCode.NRefactory.CSharp/Completion/CSharpCompletionEngine.cs line 289) inserts the following "</" + tag + ">".
But, the cursor will be set behind the closing > bracket. It would be better to place the cursor between the two tags <a>|</a> where | is the cursor.
I hope you know what I mean.
It would require many changes I suppose. Difficult - not really, but it would be required to change the whole API to support that.
It's easier to just place the caret manually in the 2-3 cases where that's required.
I just added it to our API - and implemented the basic case.
Let's see how it works out ...
Thanks a lot.
The reason I wanted that method implemented was becuase of Bug 6744, that you implemented as well. ;) Nice work