How can I change Eclipse color scheme for a specific file extension? - eclipse

I've installed Eclipse Debugger Plugin for v8.
When a Javascript file is brought up from the remote connection, it has a .chromium extension.
Acutal color scheme for *.chromium files is not ideal but I haven't been able to figure out how to change it.
I went into Window > Preferences > General > Editors > File Associations and changed *.chromium file association from "JS Editor" to "JavaScript Editor" (used for .js files edition, and having the color scheme I want.)
However making this change had no effect.
I have the "Eclipse Color Theme" add-on installed and am using Eclipse version 4.2.1.M20120914-1800 running on windows 7.

Once I right clicked on one of the .chromium files and selected "Open With->JavaScript Editor" that file came up with the same editor as the js files. Doing this once must have fixed something in eclipse because now subsequently all .chromium files open up with the other editor.

Related

No JavaScript syntax highlighting in Eclipse 2020-09

I just upgraded to Eclipse 2020-09 (4.17.0) from Eclipse Luna. After installing, I installed Eclipse Web Developer Tools 3.19 from the Marketplace, then restarted Eclipse. When I open a .js file, there is no syntax highlighting. It was fine out of the box with Luna, so is there anything extra that I need to configure in 2020-09? File associations for *.js shows this:
It seems JavaScript files (*.js) have been associated with the plain text editor instead of the Generic Text Editor by mistake (please make sure it has been reported to Eclipse).
Right-click the file and choose Open With > Generic Text Editor.
Or better, associate all *.js files with the Generic Text Editor by right-click a *.js file, choose Open With > Other..., select the Generic Text Editor in the list and tick the Use it for all '.js' files* checkbox at the bottom (as shown in my video here).
Yes, you need to install the Wild Web Developer feature so that it provides that functionality through the Generic Text Editor.

Why my Eclipse doesn't mark the reserverd words for Haskell?

I've installed the plugin for Eclipse Luna: EclipseFP - http://eclipsefp.sf.net/updates . Its Works, but the IDE is not marking the reserved words.
That looks like you are actually using the normal text editor.
Close the file and then right click on the file in Project Explorer and choose 'Open With...' and select the Haskell editor.
Eclipse remembers the last editor you used to open a file so if you had opened this file before installing the plug-in you will get the plain text editor. Once you have opened the file with the correct editor it will use that editor by default in future.

Stop XCode opening GLSL files in eclipse

I'm quite new to OSX and I would like to prevent XCode from opening GLSL files in eclipse.
I've tried changing the default program that opens this extension files in the OS, but i can't select eclipse as an option.
Open Eclipse > Preferences > General > Editors > File Associations
Add .glsl files and choose the default editor for this files. Text editor for example.

Eclipse insists on opening java files in Sublime

We recently upgraded our copies of Sublime. Problem is now our developers that use eclipse are having trouble opening java files. It seems that Eclipse has for one reason or another decided that half of the java files should be opened with "Java Editor" (when you right click and go to Open With) and the other half should open in "System Default" which as it turns out, is Sublime.
Where is the button I press to reset this stupid thing so Eclipse will open java files in Eclipse?
Eclipse "remembers" when files were "Open with"-ed with a certain Viewer and opens that file always with that Viewer from than on (it gets highlighted in the Options list and overrides the file-association).
You could try to change it back to the default by choosing "Default Editor" in the "Open with" context menu option in Project Explorer for each file that behaves strange.
The default editor for a file type can be set through Window>Preferences>General>Editors>File Associations. If multiple editors are set for .java and it's bugging out then possibly removing all editors except the default will help.

Eclipse 3.3 default editor under Vista

I switched some months ago from Eclipse 3.0 under Win2000 to Eclipse 3.3.2 under Vista.
With my old platform, when I opened a file from eclipse navigator, for which no particular editor was configured, the file was defaultly opened with LPAD editor.
Now with my new platform, in the same situation, Eclipse delegates the choice to Vista, so to keep the same behavior I have to explicitly add the "unknown" extension in Window / Preferences, menu General / Editors / File Associations, and configure it to open with eclipse text editor.
Of course ".*" si not accepted like a valid extension, so I have to do it extension by extension.
And by the way there are tons of such "unknown" extensions I work with : .launch, .cvsignore, .pmd, .ruleset, .bindings, .csv (I want to edit such with textEditor, not excel), .vm, and so on...
From eclipse navigator I can open the context menu and select, for THIS particular file, to open it with the text editor, but it does not apply to other files with the same extension.
It's worse when opening the file from Open Resource dialog box, as in this case the context menu is not even available.
In a word, is there any way to configure eclipse 3.3.2 under Vista so that any file with an unknown extension will open with a given eclipse default editor ?
You do have (since eclipse3.2):
Open With->System Editor from the context menu
alt text http://www.myeclipseide.com/modules/ContentExpress/img_repository/docs/55M1/snaps_crossover.gif
That will pick the editor the system (here Vista) currently associates with your files.
But that still leaves you with the unpleasant task to set up the proper associations within the System itself (Vista)
There are some relevant feature requests for similar use cases (but they are there for years so don't expect to implement them soon):
Default editor for unknown extensions
File Associations doesn't accept standard wildcards
Currently you have to manage each important "dot-started names" individually in File Associations as you mentioned, I suppose.