Why TextPad has to use an extension for apply a CLASS. That is Microsoft Windows' way. I Think TextPad should have a better product. The user can't enter all the extensions for all the languages.
In my case the extension doesn't matter.
TextPad should have something like this:
c:\textpad -splus filename.xyz
-splus is the class. It could be -c++, -pascal, -java. Then inmeaditily the file will show the color for that class.
It may be in the Windows menu. When the user does rigth-click, It should appear a menu with all the options available for open the file.
It will help. And in this way can work TextPad on Unix and Apple.
Bye
No extensions (*.xyz) for Textpad
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
I would add the 'no extension' case 
There are now C++ header files without extension (courtesy of STL) that I cannot view with syntax coloring.
Similarly, often UNIX text files have no extensions (e.g. README, makefile).
Suggestion: For any given open document, being able to say "treat as" (text, C++, etc), to temporarily invoke syntax coloring (or - for the no extension case for example - 'treat as until further notice').
Alternative suggestion: A special tag (inside the text file) for specifying the syntax (e.g. for makefile versus the header files, etc). In fact, this way one could use different highlighting in different parts of the same file
There are now C++ header files without extension (courtesy of STL) that I cannot view with syntax coloring.
Similarly, often UNIX text files have no extensions (e.g. README, makefile).
Suggestion: For any given open document, being able to say "treat as" (text, C++, etc), to temporarily invoke syntax coloring (or - for the no extension case for example - 'treat as until further notice').
Alternative suggestion: A special tag (inside the text file) for specifying the syntax (e.g. for makefile versus the header files, etc). In fact, this way one could use different highlighting in different parts of the same file