Bug 2296 - On the fly code formatting messes up code
Summary: On the fly code formatting messes up code
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-12-01 07:26 UTC by Chris Hardy [MSFT]
Modified: 2012-02-23 06:14 UTC (History)
2 users (show)

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


Attachments
Video of the issue (2.15 MB, video/ogg)
2011-12-01 07:26 UTC, Chris Hardy [MSFT]
Details


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:
Status:
RESOLVED FIXED

Description Chris Hardy [MSFT] 2011-12-01 07:26:15 UTC
Created attachment 980 [details]
Video of the issue

Hi. With last MonoDevelop versions (it started, I guess, in 2.8) I have problems with on the fly code formatting. When enabled, it quite frequently totally messes up fragment of code. It could be not so straightforward to reproduce this, however I had this issue (among others) in my project ELFSharp: https://github.com/konrad-kruczynski/elfsharp, which anyone can try.
Comment 2 Mike Krüger 2012-02-23 06:14:36 UTC
That one is already fixed (the code was mixing space & tab formatting, that caused that).