files with .def extension aren't associated with SDF editor until file with .sdf extension has been opened
Some strange (minor) issue I noticed today:
When you have Eclipse just started, and try to open a SDF file with a .def extension the default editor opens (plain text editor on Linux; unknown file type dialog on Windows) instead of the IMP editor. Only after you have opened at least one SDF file with a .sdf extension the IMP editor opens for .def files.
This only seems to happen for a deployed plugin (or something specific to the SDF plugin): I could not reproduce when I had the SDF editor project open in my workspace; I can always reproduce it when I do not have the SDF editor project open in my workspace.
EDIT: Note that .def is the second file extension defined for SDF and .sdf is the first. Possibly this happens for all deployed plugins with multiple file extensions.Submitted by Tobi Vollebregt on 31 December 2010 at 16:08
Ah, I found the problem. Currently,
plugin.xmlalso lists the file extensions used by an editor. When an editor is deployed (and not just dynamically loaded), this file is used. Since it’s a user-editable file we can’t just overwrite the values there; instead, we should add a warning to the
esveditor in case its extensions are inconsistent with that of plugin.xml.
The part of the issue regarding SDF specifically is fixed. A larger issue regarding this is https://yellowgrass.org/issue/Spoofax/625.
Log in to post comments