Bug 24419 - [EditorMgmt] associations: Associations do not honour *.*
Summary: [EditorMgmt] associations: Associations do not honour *.*
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-04 16:46 EDT by Jared Burns CLA
Modified: 2019-09-06 16:13 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Burns CLA 2002-10-04 16:46:05 EDT
Build 20021001

1. Add the filetype "*.*" to the editor association preference page
2. Add the editor "Text Editor" for this filetype.
3. Double-click a file named blah.xml.
4. Instead of launching the text editor, a system editor is opened.

If the filetype *.* is entered, any file which doesn't have a more specific 
association mapping should use the editor associated with *.*

Background rant:
Eclipse's default behavior for unknown filetypes is to open a "System 
editor" on it. For me (a command-line Linux user), this amounts to a 
"Random editor". I don't ever want Eclipse launching an external program 
unless I explicitly tell it to.
Comment 1 Sonia Dimitrov CLA 2002-10-07 08:44:15 EDT
Duplicate of bug 20528?
Comment 2 Jared Burns CLA 2002-10-07 09:32:45 EDT
This bug might fix Bug 20528, but fixing Bug 20528 won't fix this bug. The 
fact that the wildcard isn't handled correctly is related to, but 
independant from the default editor problem.
Comment 3 Eduardo Pereira CLA 2002-10-09 11:26:31 EDT
The file association preferences do not do match on extensions. I.E .* files 
means nothing for the current implementation since you can not have a file 
named "foo.*".

Just tried it on Windows and extension "*" does not mean anything either.
There is not sush thing as a more spectify extension. Either it the same 
extension of it is not.
Comment 4 Jared Burns CLA 2002-10-09 11:33:05 EDT
You're confusing file names with regular expressions that can match to file 
names. When the user specifies a file association to files named "*.xml", 
they're not talking about files with the literal name "*.xml". The same goes 
for "foo.*" or "foo.htm*".

If the user says they want to make an association for files named "*.htm*", 
that should mean that a file named "index.html" or "index.htm" would be match 
that association.

Expressions are "more specific" as the number of characters increases and the 
number of wildcards decreases.
Comment 5 Eduardo Pereira CLA 2002-10-09 11:53:33 EDT
It does not work like that on Windows. How does it work on Linux? Do you know? 
Can you specify "*.htm*"?

I am not thinking about regular expressions. I am saying that we get the 
extension of the file and see if it is EQUALS to the ones we have in the 
preferences page. We do not look for a better match and neither does Windows.
Comment 6 Jared Burns CLA 2002-10-09 12:14:17 EDT
I'm a little confused by your comments. Which Win32 program are you talking 
about? If you mean the file association dialog in Windows Explorer, I just 
tested it on WinXP and you *can* specify htm* as an extension there.

Eclipse's file association dialog isn't file extension based (xml, html, 
etc.), it's filename based (build.xml, project.xml, *.xml).

The problem here is that we don't correctly handle wildcards in all situations.
Comment 7 Eduardo Pereira CLA 2002-10-09 12:28:11 EDT
The problem is NOT that we don't correctly handle wildcards in all situations.
The fact is that we do not handle wildcards on extensions.

Yes I am talking about Windows Explorer. Please try the following on XP (I just 
did on Win2000). Create a extension "fo*" and associate it with notepad. Then 
create the file "abc.foo" and double click on it to see if it opens notepad.
Comment 8 Jared Burns CLA 2002-10-09 13:25:16 EDT
I haven't tried it yet, but I still don't understand why the MS Windows 
behavior is relevant here. Are we really interested in emulating Windows 
Explorer bugs/deficiencies?
Comment 9 Jared Burns CLA 2002-10-09 13:37:20 EDT
Oh, and I didn't mean that we handle wildcards incorrectly in all situations. 
:) I meant that we don't handle them correctly in all possible cases. That is, 
there are positions that the user can place a wildcard which we don't handle.
Comment 10 Eduardo Pereira CLA 2002-10-09 13:44:38 EDT
No, but I am interested to know how it works in other apps specialy Windows and 
Linux. That why I asked you how it works on Linux and I told you that it does 
not work on Win2000.
Comment 11 Michael Van Meekeren CLA 2006-04-21 13:18:53 EDT
Moving Dougs bugs
Comment 12 Susan McCourt CLA 2009-07-09 19:02:13 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 13 Boris Bokowski CLA 2009-11-17 13:06:13 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 14 Eclipse Webmaster CLA 2019-09-06 16:13:01 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.