While editing a file of a type that is not part of the Language menu properties files , we can still have keyworld highlighting because this file type is (joined) to another language file.
or
Sometime, you try different Language filter on a file to select a close match for further modification...
It would be useful to Highlight the Language currently in-use so we do not have to go true the properties files to figure it out.
The current state is a composite of various settings and, as a whole, does not correspond to an item in the Language menu.
Is there a reason to not bind these settings to the relates menu entries?
Please explain the proposed behaviour in detail.
For example if I'm opening a python file the syntax highlighting will choose "Python". The feature request here is that after opening the menu entry "Language" there could be something like a circle to the left of "Python" so that we can see which syntax highlighting is applied to the related file.
Is it supposed to do anything if the user does not choose an item from the Language menu? How would that work? That is part of what I wanted by 'in detail'.
I think we have some sort of communication problem here. I will explain it with pictures. default.png is what SciTE currently looks and extended.png is what I would like to see.
What is the set of rules which determine which menu item to select?
I don't think there is a sensible set of rules which would cover most uses of SciTE and will not cause users to be confused.
I don't know how to solve this explicit in SciTE because I doesn't know the sourcecode of SciTE. I do just know that there is a logical relationship between autodetection and explicit setting of the syntax highlighting with a menu entry which should it make theoretically possible to implement this.
Last edit: Sworddragon 2013-07-25