Bug 17391 - [EditorMgmt] Jar files should not be opened with Default Text Editor
Summary: [EditorMgmt] Jar files should not be opened with Default Text Editor
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 17765 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-23 12:20 EDT by Eduardo Pereira CLA
Modified: 2019-09-06 15:37 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eduardo Pereira CLA 2002-05-23 12:20:36 EDT 
Build F1.

Instead of opening files that does not have an editor associated with the 
Default Text Editor, we could ask to user for an editor. Like Windows does.

Opening a JAR file with a default text editor is useless.
Comment 1 Eduardo Pereira CLA 2002-05-23 12:24:16 EDT 
Not sure why zip files are not opened in the Default Text Editor as well.
If a open a zip or jar in the Windows File Explorer the WinZip opens.

I do not have file bindings for either jar or zip. Why does it open zip as it 
should (external winzip) but does not do the same for jar files.
Comment 2 Nick Edgar CLA 2002-05-27 23:26:10 EDT 
If there's a system binding for .zip, then we use the system editor, otherwise 
the text editor.
Comment 3 Eduardo Pereira CLA 2002-09-06 10:23:39 EDT 
*** Bug 17765 has been marked as a duplicate of this bug. ***
Comment 4 Michael Van Meekeren CLA 2006-04-21 13:19:17 EDT 
Moving Dougs bugs
Comment 5 Susan McCourt CLA 2009-07-09 19:01:54 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 6 Boris Bokowski CLA 2009-11-17 13:03:57 EST 
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:37:04 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.

If you have further information on the current state of the bug, please add it. 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.