Bug 1046 - MonoDevelop should not automatically jump to the file with the first compile error
Summary: MonoDevelop should not automatically jump to the file with the first compile ...
Status: RESOLVED FEATURE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-09-25 18:39 UTC by Alan McGovern
Modified: 2011-09-26 05:37 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FEATURE

Description Alan McGovern 2011-09-25 18:39:40 UTC
When refactoring code I typically can have a couple of dozen compile errors in a class. I usually fix a few of these and then hit 'compile' to ensure everything I just modified compiles as expected. MonoDevelop keeps automatically switching to a different file, the file where the first compile error was found. This is really annoying as I constantly end up having to switch back to the file I was originally working on.

Can this behaviour be removed, or alternatively can it be enhanced so that it does not jump away from a file if the file I already have open has compile errors in it?

Personally, I'd much prefer if it never jumped away from the file I'm currently editing as even if what I just wrote compiles perfectly, I may still want to make more changes.
Comment 1 Mike Krüger 2011-09-26 05:36:56 UTC
It can be turned off - miguel choosed that as default during the introduction of message bubbles.
It can be turned off on the same page as the error bubbles therefore :)

I like that feature btw.