Bug 11380 - Editor closes immediately after removing file physically
Summary: Editor closes immediately after removing file physically
Status: RESOLVED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.3
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2013-03-24 09:47 UTC by alex
Modified: 2013-07-26 03: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 INVALID

Description alex 2013-03-24 09:47:38 UTC
How to reproduce:
1) Open any file in MD's text editor
2) Delete/Move the previously opened file in the OS's file system
3) Refocus MD
4) File gets closed w/o asking me whether I want to save/'restore' the file -- that's a major issue e.g. when working on network drives or unstable drive mounts

It should at least mark the file as dirty and/or ask the user to save it under an other file name!

Original issue report:
https://github.com/aBothe/Mono-D/issues/249
Comment 1 Mike Krüger 2013-03-26 03:27:46 UTC
fixed
Comment 2 Mike Krüger 2013-07-26 03:37:13 UTC
I reverted the fix.

See discussion about that in:

https://bugzilla.xamarin.com/show_bug.cgi?id=11937