Bug 6764 - Saving makes local variables turn red
Summary: Saving makes local variables turn red
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-08-30 15:36 UTC by Arturo Espinosa
Modified: 2012-10-08 06:36 UTC (History)
1 user (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 Arturo Espinosa 2012-08-30 15:36:22 UTC
Sometines when you hit Ctl-S on a file, all local variables will turn red as if they weren't declared. If you trivially modify the file (add a space, then remove it with bsp) and save again, all goes back to normal.
Comment 1 Arturo Espinosa 2012-08-30 15:36:47 UTC
These are normal C# files, btw.
Comment 2 Mike Krüger 2012-08-31 01:21:04 UTC
Which monodevelop version are you using ?
Have you turned on format on save ?
Does it happen every time or only sometimes ?
Comment 3 Arturo Espinosa 2012-08-31 02:23:11 UTC
Latest monodevelop from git's trunk, compiled yesterday.
I'm using format-on-save, yes.
Only sometimes, but I haven't had the time to find a minimum test case. These are files for Gtk widgets or windows (partial classes with some code generated automtically by Stetic in another file). I'll report if it happens with plain classes (no Stetic) tomorrow as I keep working. I'm paying attention to my coding activity to see what is triggering it, but so far it seems pretty random.
Comment 4 Arturo Espinosa 2012-08-31 02:24:22 UTC
Oh, and thanks for your work.
Comment 5 Mike Krüger 2012-10-08 06:36:29 UTC
I've rewritten the semantic highlighting algorithm - let's hope it works :)