Below is a busy nonsense example showing the contents of a text file view. It shows a complex primary command, some excluded lines, a column number line, a tabs position line, line labels, global line commands, and a message saying a command is pending.

Below is an example of a 'FList' view. It shows a list of file and directory entries with the files being listed at the top and directories/folders listed at the bottom (the order type is an option that can be set in the profile file). There are columns of data showing basic attributes of: size, date, and entry names. The column on the left is where line commands can be entered, such as: edit, view, delete lines, move lines, exclude lines, etc. As an example, 'e' or 'v' would edit or view a file/directory. And primary commands such as 'x', 'f' or 'sort' can exclude, find text, or sort lines of entries. The Windows and Unix views both look pretty much the same, except that the Unix version can show symbolic links like that shown in the 'wte0Mwn5.rc' file name. As a note, in this example the author uses the character '!' as the primary command group separator character (an option that can be set in the profile file).

Besides the copy, paste, and copy from file stuff, there are global line commands that allow you to copy or move lines (GC/GM) or a block of lines (GCC/GMM) from one file view to another (GA). Further, these commands can be stacked so you are not constantly switching back and forth between views.

Word wrapping is either continuously ON (like the SPF TE feature) or continuously OFF and can be controlled via a primary command, but generally it is set by a configuration entry in the directory profile files. This makes it easy to utilize the editor for writing letters and documents in one directory, but in another directory can be set for things like programming and columnized data. Even the paste operation follows the word wrap setting. Word wrapping happens when text entry goes beyond the width of the window. And the window width can be set via the profile file as well.

To further configure CWTE, there are three possible profile files that will be searched for. Where any combination may or may not exist. First, there is only one optional GLOBAL profile file for anywhere use of the editor that generally defines the overall default usage of the editor and is the first to be processed. Then, depending on where CWTE starts up, the next optional profile file that would be processed is that found in the parent directory (the intent of this file is that it would be shared by one or more common directories for a class of work). The last optional profile file would be located in the default directory where CWTE started up at. Each of these allows for a more specific use of the editor in a given directory. Directory profile files can be located anywhere, but only those as described at start up time will be used. These profile files and their configuration assignments will provide common portability across the supported platforms. Note however, that the profile files are not needed if you are willing to use the built-in defaults, but most likely you will have your own preferences.

CWTE has been designed to operate across several platforms and to work very much the same on each of them. Features were even added to deal with keys on laptops: the lack of, the multi use of, and even configuring keys for the IBM 3270 feature. All FKey can be [re]assigned. As time went on, still other features were added as special little wishes came into mind. Through all of this, the features between the Linux/Unix and Windows versions were implemented to be as close in function as possible. Such as using the line and primary commands to launch applications, web pages, etc.

CWTE is only a text editor. It only uses the basic ASCII text and does not support Unicode or EBCDIC characters. Is only implemented in the English language. The primary command field is located only at the top part of the window. There is no line numbering, but the area is still used for line commands.

If after looking over CWTE, having given CWTE a try, and you still feel this SPF-Like Editor is not the answer for you, you might want to then go over to Dave's SPF Editor Page to check out the variety of other SPF-Like Editors that Dave has been tracking.