Bug 549617 - New Untitled Text Files cannot be auto-saved
Summary: New Untitled Text Files cannot be auto-saved
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-29 03:34 EDT by Ed Willink CLA
Modified: 2021-07-19 02:11 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2019-07-29 03:34:12 EDT
The ability to create New Untitled Text Files is nice, but it has a severe drawback. By default the new file is dirty and unsaveable, so that any action that triggers a save-all pops up a dialog demanding to know where to save it. Reasonable, but...

Bug 1: Cancelling this dialog cancels the whole save-all, leaving other files unexpectedly dirty. Canceling should only cancel the Untitled Text File saves.

Bug 2: On Windows, an OS update can now occur with only brief warnings to the user and after a bit the update just happens regardless, so if an Eclipse is active, Eclipse is triggered to save and shut down, but if there is an Untitled Text File, the file save fails and consequently the workspace save fails too. At least the resulting workspace is not corrupt, but many preferences get lost or reset.

Solution:

Let all New Untitled Text File have a default location, probably a subfolder of the user's home directory so that save can happen when Eclipse is shutting down. If no shutdown is in progress, the existing dialog can still demand a proper save location that can be used as the default.

Major, since the current functionality enables Windows Update to corrupt the user's workspace.
Comment 1 Eclipse Genie CLA 2021-07-19 00:03:29 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Ed Willink CLA 2021-07-19 02:11:51 EDT
Surely needs a relevant committer to triage before being CLOSED?