Page 1 of 1
applying syntax coloring to files without extentions
Posted: Thu Apr 03, 2003 6:14 am
by bwvoris
C++ header files have (per the standard) no extension. For example <string>. (That is, extensions such as .hpp, etc. are deprecated.)
Is there a way to tell TextPad that this file without an extension is C++, whereas that file without extension is not?
Thanks.
applying syntax coloring to files without extentions
Posted: Thu Apr 03, 2003 11:42 am
by SteveH
While you can apply syntax colouring to files without extensions it will apply to all files of that type.
The practicalities are that you need to add the filter '*.' to the document classes (remembering to remove this from the text document class).
applying syntax coloring to files without extentions
Posted: Thu Apr 03, 2003 5:20 pm
by bwvoris
Helios, are you listening?
We need a something like a "format as" command. Once that's in place, I'd like the workspace to remember the file type of files without an extension. For example, "string" is C++, but "make" is a make file.
Files I commonly see without extensions are HTML, C++, and make files. Changing '*.' isn't really an option, because I commonly have all last two open at once.
Posted: Fri Apr 04, 2003 10:56 am
by MudGuard
We need a something like a "format as" command.
View -> Document Properties -> Syntax ...
Once that's in place, I'd like the workspace to remember the file type of files without an extension.
As far as I have tested, a workspace saves the setting made under View -> Document Properties...
Is there a way to tell TextPad that this file without an extension is C++, whereas that file without extension is not?
See above, yes, and together with workspaces the info is saved.
applying syntax coloring to files without extentions
Posted: Fri Apr 04, 2003 6:11 pm
by bwvoris
This works for me.
Thanks!
(Now, if I could just give TextPad a list of files, not extensions, that would be even better -- but I'm not complaining.)
Posted: Fri Apr 04, 2003 10:35 pm
by Bob Hansen
You commented:
Now, if I could just give TextPad a list of files, not extensions, that
would be even better -- but I'm not complaining.)
This should solve your problem:
Start TextPad with the command option @filename.
This will open all the files that are listed, one per line, in the specified file. This overrides the option to load the workspace, specified on the General page of the Preferences dialog box.
See "Command Line Parameters" in the Help Section. Lots of useful options there.