Bug 11784 - opening curly brace is erased by editor
Summary: opening curly brace is erased by editor
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-04-14 18:42 UTC by Michael Rutherford
Modified: 2013-04-15 20:58 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Michael Rutherford 2013-04-14 18:42:11 UTC
If I place my cursor immediately to the right of an opening curly brace, a small orange highlight appears on the matching closing curly brace. Pressing [Enter] will go to the next line, indented properly.

If I poke around a little, I can get the cursor to the right of the opening curly brace with *NO* orange highlight.

Once this happens, pressing [Enter] will erase the opening curly brace.

This can be incredibly irritating since once the curly is gone, intellisense proposes really weird names, and auto-complete kicks in - leading to a bunch of ctrl-Z's.

This started happening on the latest update.
Comment 1 Mike Krüger 2013-04-15 17:11:28 UTC
already fixed.
Comment 2 Michael Rutherford 2013-04-15 20:58:42 UTC
Perfect ... Thanks :)