- Aug
- 2,314
- 111
From the help file;
The library files,
that I have created and use with TCC,
have the extension .library
When using TCEdit to edit the source of my .library files,
I get no syntax colorization.
I could rename my source.library to source.btm,
TCEdit source.btm,
and then rename source.btm back to source.library,
just to get syntax colorization.
I was wondering if an option could be added to TCEdit
to allow the user to alias an existing file extension,
for example, .btm
to the .library or .lst extension,
for example,
which would allow syntax colorization to be used,
in my case,
for the .library extension,
based on the .btm extension.
Joe
Code:
TCEDIT will select the syntax lexer (colorization) based on the file extension:
.bat TCMD (or CMD)
.btm TCMD
.cmd TCMD (or CMD)
.css CSS
.htm HTML
.html HTML
.lua Lua
.php PHP
.pl Perl
.ps1 PowerShell
.py Python
.rb Ruby
.sh Bash shell
.sql SQL
.tcl Tcl/Tk
.vbs VBScript
.xml XML
The library files,
that I have created and use with TCC,
have the extension .library
When using TCEdit to edit the source of my .library files,
I get no syntax colorization.
I could rename my source.library to source.btm,
TCEdit source.btm,
and then rename source.btm back to source.library,
just to get syntax colorization.
I was wondering if an option could be added to TCEdit
to allow the user to alias an existing file extension,
for example, .btm
to the .library or .lst extension,
for example,
which would allow syntax colorization to be used,
in my case,
for the .library extension,
based on the .btm extension.
Joe