|
SciTE Documentation |
| Frequently Asked Questions Scripting Regular Expressions |
Text editing in SciTE works similarly to most Macintosh or Windows editors with the added feature of automatic syntax styling. SciTE can hold multiple files in memory at one time but only one file will be visible. Rectangular blocks of text can be selected in SciTE by holding down the Alt key on Windows or the Ctrl key on GTK while dragging the mouse over the text. The modifier key used on GTK can be changed with the rectangular.selection.modifier property.
There are two panes in SciTE, the editing pane and the output pane. The output pane is located either to the right of the editing pane or below it. Initially it is of zero size, but it can be made larger by dragging the divider between it and the editing pane. The Options | Vertical Split command can be used to move the output pane beneath the editing pane.
SciTE can perform commands to compile or run source files with the output from these commands directed into the output pane.
For example, if Python is installed on the machine, open a new document, type:
print("hi")
as that document's text.
Save the document as printhi.py.The document should now appear coloured as SciTE is using the file's extension to decide upon the syntax styling to use:
print("hi")
Perform the Tools | Go command.The output window will be made visible if it is not already visible and will show:
>pythonw -u printhi.py
hi
>Exit code: 0
The first blue line is from SciTE showing the command it will use to run the program. The black
line is the output from running the Python program. The last blue line is from SciTE showing
that the program has finished and displaying its exit code. An exit code of zero indicates a
successful run. <p>
SciTE partially understands the error messages produced by Python, GCC, Visual C++, Borland
C++, PHP and other tools which use the same format as one of these. To see this, add a mistake to
the Python file by adding a second line to make the file:
</p>
<blockquote>
<code>
<span style="color:#000080;font-weight:bold;">print</span><span style="color:#000000;font-weight:bold;">(</span><span style="color:#800080;">"hi"</span><span style="color:#000000;font-weight:bold;">)</span>
<br />
mistake
</code>
</blockquote>
<p>
Perform the Tools | Go command. The results should look like:
</p>
<blockquote>
>pythonw -u printhi.py hi Traceback (most recent call last): File "printhi.py", line 2, in <module> mistake NameError: name 'mistake' is not defined >Exit code: 1
</blockquote>
<p>
While it is easy to see where the problem is in this simple case, when a file is larger the
Tools | Next Message command can be used to view each of the reported errors. Upon performing
Tools | Next Message, the first error message in the output pane is highlighted with a yellow
background, and an error indicator is displayed for the appropriate line in the editing pane.
The caret is moved to this line and the pane is scrolled if needed to show the line. SciTE
now looks like this:
</p>
<img src="PrintHi.png" alt="SciTE after running Python interpreter" />
<p>
SciTE understands both the file name and line number parts of error messages in most cases
so can open another file (such as a header file) if errors were caused by that file. This
feature may not work where the file name is complicated by containing spaces or ".."
</p>
<p>
If command execution has failed and is taking too long to complete then the Tools | Stop
Executing command can be used.
</p>
<h3 id="CommandSubsystem">
Command subsystem
</h3>
<p>
Tools can be executed in various modes by SciTE which are called "subsystems". Different
subsystems are supported on Windows, GTK and macOS. The default subsystem is 0.
</p>
<table class="windowsonly" cellpadding="0" cellspacing="0" border="1" summary="Command line commands">
<thead><tr><td colspan="3">Windows</td></tr></thead>
<tr><td>0</td><td>console</td><td>Command line programs<br/>Do not use for GUI programs as their windows will not be visible.</td></tr>
<tr><td>1</td><td>windows</td><td>Programs that create their own windows</td></tr>
<tr><td>2</td><td>shellexec</td><td>Run using ShellExecute<br />
A good way to open HTML files and
similar as it handles this similarly to a user opening the file from the shell.</td></tr>
<tr><td>3</td><td>lua<br />director</td><td>Internal extension or director extension</td></tr>
<tr><td>4</td><td>htmlhelp</td><td>Open in HtmlHelp program<br />
Two part command separated by ! with the first
part being the topic to search for and the second the name of the help file
</td></tr>
<tr><td>5</td><td>winhelp</td><td>Open with WinHelp function<br />
Two part command similar to subsystem 4</td></tr>
<tr><td>7</td><td>immediate</td><td>Internal script that is executed immediately instead of being queued.</td></tr>
</table>
<br />
<table class="gtkonly" cellpadding="0" cellspacing="0" border="1" summary="Command line commands">
<thead><tr><td colspan="3">GTK and macOS</td></tr></thead>
<tr><td>0</td><td>console</td><td>Execute tool and wait for it to finish</td></tr>
<tr><td>2</td><td>shellexec</td><td>Execute in background</td></tr>
<tr><td>3</td><td>lua<br />director</td><td>Internal extension or director extension</td></tr>
<tr><td>7</td><td>immediate</td><td>Internal script that is executed immediately instead of being queued.</td></tr>
</table>
<h3 id="CommandLineArguments">
Command line arguments
</h3>
<p>
Command line arguments to SciTE include file names, commands and properties.
Commands and properties are preceded by "-" and are differentiated by the use in
commands of ':' as the first character that is not '.' or alphabetic.
Properties use the syntax used in property set files and override any
properties set in property files. If there is no value given for a property, it is set to 1.
Double quotes may be placed around arguments that contain spaces but they must be
placed around the whole argument, not just around a file name, so "-open:x y.txt" works but
-open:"x y.txt" doesn't.
On Linux, the standard shell quoting is available.
The "-p" argument causes SciTE to print the file and then exit.
</p>
<p>
For <span class="windowsonly">Windows</span>:<br />
The command line arguments "-" and "--" (without the quotes) are special in that they read the
stdin stream into the last buffer ("-"), or the output pane ("--"))<br />
The command line argument "-@" (without the quotes) is special in that file names are read from stdin
and opened.<br />
<b>Note:</b> when reading stdin into the output pane, when the property split.vertical is 0, the
output pane is increased to its maximum height. When the property split.vertical is 1, the output pane is
increased to approximately half of the screen width.<br />
<b>Note:</b> If stdin is not redirected, these arguments are effectively ignored.
</p>
<div>
For example,</div>
<div class="example">
SciTE "-font.base=font:MS Gothic,size:11" -save.recent ScintillaGTK.cxx
</div>
<div>starts SciTE, opens ScintillaGTK.cxx, loads the recent file list, and uses
11 point MS Gothic as the base font.<br />
A group of properties can be saved as a property set file (with the extension
".properties") and the import command used on the command line:</div>
<div class="example">
SciTE "-import c:\os\web_work" SciTEDoc.html
</div>
<p>
A few commands are currently available although this will expand in the future.
These commands are available:</p>
<table cellpadding="0" cellspacing="0" border="1" summary="Command line commands">
<thead>
<tr><th>Command</th><th>Argument</th></tr>
</thead>
<tr><td>close:</td><td></td></tr>
<tr><td>cwd:</td><td>change working directory</td></tr>
<tr><td>find:</td><td>search text</td></tr>
<tr><td>goto:</td><td>line number[,column number]</td></tr>
<tr><td>open:</td><td>file name</td></tr>
<tr><td>loadsession:</td><td>file name</td></tr>
<tr><td>quit:</td><td></td></tr>
<tr><td>replaceall:</td><td>search text\000replacement text</td></tr>
<tr><td>saveas:</td><td>file name</td></tr>
</table>
<br />
Commands use C style escape sequences which include:
<table cellpadding="0" cellspacing="0" border="1" summary="Command line escape sequences">
<thead>
<tr><th>Escape Sequence</th><th>Meaning</th></tr>
</thead>
<tr><td>\\</td><td>backslash</td></tr>
<tr><td>\a</td><td>bell</td></tr>
<tr><td>\b</td><td>backspace</td></tr>
<tr><td>\f</td><td>form feed</td></tr>
<tr><td>\n</td><td>new line</td></tr>
<tr><td>\r</td><td>carriage return</td></tr>
<tr><td>\t</td><td>tab</td></tr>
<tr><td>\v</td><td>vertical tab</td></tr>
<tr><td>\<ooo></td><td>octal number specified by 1, 2, or 3 digits</td></tr>
<tr><td>\x<hh></td><td>hexadecimal number specified by 2 digits</td></tr>
</table>
Windows paths normally use "\" to separate directories and these should be doubled in commands.
"/" may be used instead to separate directories on Windows.<br />
The following opens /big/icon.txt:<br />
<div class="example">
SciTE -open:/big/icon.txt
</div>
On Windows, the following opens C:\Program Files\SciTE\SciTEDoc.html
and goes to the 123rd line:<br />
<div class="example">
SciTE "-open:C:\\Program Files\\SciTE\\SciTEDoc.html" -goto:123
</div>
<p>
Command line arguments are evaluated left to right in two phases because
opening files requires the user interface to be available and there is also a need
to set some user interface properties before the user interface is displayed.
The first phase process arguments until just before the first file name would be opened.
The second phase processes the remaining arguments.
</p>
<p>
So, if you need to perform e.g. a find: or a goto: command on a file, you must put
the command after the filename, to allow SciTE to open the file before performing the command.
</p>
<p>
For <span class="windowsonly">Windows</span>:<br />
If any simple file name on the command line matches a directory name, the file open dialog appears - this is dependent upon the property
"open.dialog.in.file.directory"<br /><br />
If the property "buffers" is greater than one and the file name matches either a existing file or by means of a wildcard search, one or more files, the
matching files are loaded up to the property "buffers" count. Directories are not considered a match in this case<br /><br />
If the file name is an extension, optionally preceded by a path, and no such simple file name exists, the file open dialog appears, with the given extension as
the filter.<br /><br />
If the file name contains no extension, the property "source.default.extensions" is used to provide default extensions to attempt to match the file name to an
existing file.
</p>
<h3 id="Buffers">
Buffers
</h3>
<p>
SciTE may be configured to use between 1 and 100 buffers each containing a
file. The default is 1 and this effectively turns off buffers. With more than one buffer,
the Buffers menu can be used to switch between buffers, either by selecting the
file name or using the Previous (F6) and Next (Shift+F6) commands.
A tab is displayed for each buffer in the tab bar although this can be turned off with the
View | Tab Bar command.
A tab may be closed by clicking on it with the middle mouse button.
Setting large numbers of buffers may cause problems as some menus are fixed in length
and thus files beyond that length may not be accessible.
</p>
<p>
When all the buffers contain files, then opening a new file causes a buffer to be reused
which may require a file to be saved. In this case an alert is displayed to ensure the user
wants the file saved.
</p>
<h3 id="Sessions">
Sessions
</h3>
<p>
A session is a list of file names. You can save a complete set of your
currently opened buffers as a session for fast batch-loading in the
future.
Sessions are stored as properties files with the extension ".session".
</p>
<p>
Use File | Load Session and File | Save Session to load/save sessions.
You can turn on/off "last session autoloading" using SciTE properties
variable "save.session".
</p>
<p>
If "buffers" variable is set to "0" session management is turned off.
</p>
<p>
Loading previously saved session will close your currently opened
buffers. However you will not lose your edits, because you will be
asked to save unsaved buffers first.
</p>
<p>
Opening a specific file from command line overrides "save.session"
variable state. When you start SciTE loading a specific file from
command line last session will not restore even if "save.session"
variable is set to "1". This makes "save.session" safe to use - you
will never open a couple of files when you are trying to open just
one, specific file.
</p>
<p>
By setting "session.bookmarks" and "session.folds" variables bookmarks
and folding states of the currently opened buffers are saved in session
files and restored when sessions are loaded.
</p>
<h3 id="Languages">
Languages understood by SciTE
</h3>
<p>
SciTE currently is able to syntax style these languages (* denotes
support for folding):
</p>
<ul>
<li>Abaqus*</li>
<li>Ada</li>
<li>ANS.1 MIB definition files*</li>
<li>APDL</li>
<li>Assembler (NASM, MASM)</li>
<li>Asymptote*</li>
<li>AutoIt*</li>
<li>Avenue*</li>
<li>Batch files (MS-DOS)</li>
<li>Baan*</li>
<li>Bash*</li>
<li>BlitzBasic*</li>
<li>Bullant*</li>
<li>C/C++/C#*</li>
<li>Clarion*</li>
<li>cmake*</li>
<li>COBOL</li>
<li>Coffeescript</li>
<li>conf (Apache)*</li>
<li>CSound*</li>
<li>CSS*</li>
<li>D</li>
<li>diff files*</li>
<li>E-Script*</li>
<li>Eiffel*</li>
<li>Erlang*</li>
<li>Flagship (Clipper / XBase)*</li>
<li>Flash (ActionScript)*</li>
<li>Fortran*</li>
<li>Forth*</li>
<li>GAP*</li>
<li>Gettext</li>
<li>Go*</li>
<li>Haskell</li>
<li>HTML*</li>
<li>HTML with embedded JavaScript, VBScript, PHP and ASP*</li>
<li>Gui4Cli*</li>
<li>IDL - both MSIDL and XPIDL*</li>
<li>INI, properties* and similar</li>
<li>InnoSetup*</li>
<li>Intel HEX*</li>
<li>Java*</li>
<li>JavaScript*</li>
<li>JSON and JSON-LD</li>
<li>KiXtart</li>
<li>LISP*</li>
<li>LOT*</li>
<li>Lout*</li>
<li>Lua*</li>
<li>Make</li>
<li>Matlab*</li>
<li>Maxima*</li>
<li>Metapost*</li>
<li>MMIXAL</li>
<li>MSSQL</li>
<li>Modula 3</li>
<li>Nimrod</li>
<li>nnCron</li>
<li>NSIS*</li>
<li>Objective C</li>
<li>Objective Caml*</li>
<li>Opal</li>
<li>Octave*</li>
<li>Pascal/Delphi*</li>
<li>Perl, most of it except for some ambiguous cases*</li>
<li>PL/M*</li>
<li>Progress*</li>
<li>PostScript*</li>
<li>POV-Ray*</li>
<li>PowerBasic*</li>
<li>PowerShell*</li>
<li>PowerPro</li>
<li>PureBasic*</li>
<li>Python*</li>
<li>R*</li>
<li>Rebol*</li>
<li>Registry</li>
<li>Ruby*</li>
<li>Rust</li>
<li>Scheme*</li>
<li>scriptol*</li>
<li>SORCUS Installation</li>
<li>Specman E*</li>
<li>Spice</li>
<li>Smalltalk</li>
<li>SQL and PLSQL</li>
<li>S-Record</li>
<li>Swift</li>
<li>TADS3*</li>
<li>TeX and LaTeX</li>
<li>Tcl/Tk*</li>
<li>Vala*</li>
<li>VB and VBScript*</li>
<li>Verilog*</li>
<li>VHDL*</li>
<li>XML*</li>
<li>YAML*</li>
</ul>
<p>
Running and building commands for some of these languages have been set up but should be
checked as they will have to be modified to work for many people.
</p>
<p>
To keep menus to a reasonable length some languages are included but have been commented
out in global options. These should be enabled by removing the comment character '#'.
</p>
<p>
Language settings are determined from the file extension but this can be changed
by selecting another language from the Language menu. The language menu can be
changed with the menu.language property.
</p>
<h3 id="FindReplace">
Find and Replace
</h3>
<p>
Either dialogs or strips may be used for find and replace, with dialogs being the default.
Strips are similar to find in web browsers, appearing at the bottom of the
window and are smaller and less distracting than dialogs.
They are specified with the find.use.strip and replace.use.strip properties.
</p>
<p>
SciTE has options to allow searching for words, regular expressions,
matching case, in the reverse direction, wrapping around the end of the
document.
C style backslash escapes which are listed in the command line
arguments section, may be used to search and replace control
characters.
Replacements can be made individually, over the current selection or
over the whole file. When regular expressions are used tagged
subexpressions can be used in the replacement text.
Regular expressions will not match across a line end.
</p>
<p>
SciTE supports
<a href="SciTERegEx.html">basic regular expressions</a>
with tagging.
</p>
<p>
On Windows, pressing Shift+Enter when the focus is in a text entry field will search
in the opposite of the current direction, so will normally search backwards.
</p>
<h3 id="Keyboard">
Keyboard commands
</h3>
<p>
Keyboard commands in SciTE mostly follow common Windows and GTK conventions.
All movement keys (arrows, page up/down, home and end)
allow to extend or reduce a stream selection when holding the Shift key,
and a rectangular selection when holding the Shift and Alt keys.
Some keys may not be available with some national keyboards or because
they are taken by the system such as by a window manager on GTK.
The user.shortcuts setting may be used to assign a key to a function.
Note that Home key behaviour is changed by the vc.home.key option.
Keyboard equivalents of menu commands are listed in the menus.
macOS keys differ from the other platforms with the command key ⌘
often used where the Ctrl key is used on Windows and GTK.
Some less common commands with no menu equivalent are:
</p>
| Command | Key | macOS Key ⇧ shift ⌃ control ⌥ option ⌘ command |
|---|---|---|
| Magnify text size. | Ctrl+Keypad+ | Trackpad expand gesture |
| Reduce text size. | Ctrl+Keypad- | Trackpad reduce gesture |
| Restore text size to normal. | Ctrl+Keypad/ | |
| Cycle through recent files. | Ctrl+Tab | F6 |
| Indent block. | Tab | tab |
| Dedent block. | Shift+Tab | ⇧tab |
| Delete to start of word. | Ctrl+BackSpace | ⌘delete |
| Delete to end of word. | Ctrl+Delete | fn⌘delete |
| Delete to start of line. | Ctrl+Shift+BackSpace | ⇧⌘delete |
| Delete to end of line. | Ctrl+Shift+Delete | fn⇧⌘delete |
| Go to start of document. | Ctrl+Home | ⌘↑ |
| Extend selection to start of document. | Ctrl+Shift+Home | ⇧⌘↑ |
| Go to start of display line. | Alt+Home | fn⌥← |
| Go to end of document. | Ctrl+End | ⌘↓ |
| Extend selection to end of document. | Ctrl+Shift+End | ⇧⌘↓ |
| Go to end of display line. | Alt+End | fn⌥→ |
| Expand or contract a fold point. | Ctrl+Keypad* | |
| Select to next bookmark. | Alt+F2 | |
| Select to previous bookmark. | Alt+Shift+F2 | |
| Find selection. | Ctrl+F3 | |
| Find selection backwards. | Ctrl+Shift+F3 | |
| Scroll up. | Ctrl+Up | |
| Scroll down. | Ctrl+Down | |
| Line cut. | Ctrl+L | ⌘L |
| Line copy. | Ctrl+Shift+T | ⇧⌘T |
| Line delete. | Ctrl+Shift+L | ⇧⌘L |
| Line transpose with previous. | Ctrl+T | ⌘T |
| Selection duplicate. | Ctrl+D | ⌘D |
| Find matching preprocessor conditional, skipping nested ones. | Ctrl+K | |
| Select to matching preprocessor conditional. | Ctrl+Shift+K | |
| Find matching preprocessor conditional backwards, skipping nested ones. | Ctrl+J | |
| Select to matching preprocessor conditional backwards. | Ctrl+Shift+J | |
| Previous paragraph. Shift extends selection. | Ctrl+[ | ⌘[ |
| Next paragraph. Shift extends selection. | Ctrl+] | ⌘] |
| Previous word. Shift extends selection. | Ctrl+Left | ⌃← |
| Next word. Shift extends selection. | Ctrl+Right | ⌃→ |
| Previous word part. Shift extends selection | Ctrl+/ | ⌘/ |
| Next word part. Shift extends selection. | Ctrl+\ | ⌘\ |
| Rectangular block selection. | Alt+Shift+Movement | ⇧⌥Movement |
| Extend rectangular selection to start of line. | Alt+Shift+Home | |
| Extend rectangular selection to end of line. | Alt+Shift+End |
On Windows, a search can be performed in the opposite direction by using Shift+Enter in the Find or Replace strips or dialogs.
To use an abbreviation, type it and use the Expand Abbreviation command or the Ctrl+B key. The abbreviation is replaced by an expansion defined in the Abbreviations file. You can open the Abbreviations file with a command in the Options menu and add abbreviations. There is a default abbreviations file but a different abbreviations file can be set for particular file extensions.
Each line in the files looks like "abbreviation=expansion".
The abbreviations names can have any character (except perhaps control chars,
surely for CR and LF), including high Ascii chars (accented chars).
Names have properties files limits: they cannot start with sharp (#) or space or tab
(but can have spaces inside); and they cannot have '=' character inside.
Abbreviations names are limited to 32 characters. It is probably enough for
abbreviations...
An expansion may contain new line characters indicated by '\n' and
a caret position indicated by the '|' character. To include a literal '|'
character, use '||'.
Some simple examples are included in the distributed Abbreviations file.
When expanding, the names don't need to be separated from the previous text.
Ie. if you define 'é' as 'é', you can expand it inside a word.
When multiple abbreviation names match, the longest matching name will be expanded.
SciTE supports folding for many languages (see the list of languages understood by SciTE for more information.) Fold points are based upon indentation for Python and on counting braces for the other languages.
<p>
The fold point markers (in the fold margin) can be clicked to expand and
contract folds. Normal clicking does not alter the fold state of child fold
points; naturally the children are hidden when the parent fold is
contracted, but when the parent is expanded again, each child is still
folded or not, as before.
</p>
<p>
Ctrl+Click on a fold point toggles it and performs the same operation on
all children.
</p>
<p>
Shift+Click on a fold point does not toggle that fold, it expands all the
child folds.
</p>
<p>
Ctrl+Shift+Click in the fold margin expands or contracts all the top level
folds.
"Toggle all folds" in the View menu does the same; it toggles only
top-level folds.
</p>
<p>
Tip:
To open a large code block with all its children folded, fold it with
Ctrl+Click, then open it with a normal click. Then on opening a child fold,
you will see that the grandchild folds are still closed; if you want those
'grandchild' folds open, Shift+Click the child fold.
</p>
<h3 id="PropertiesFile">
Properties file
</h3>
<p>
Much of SciTE's behaviour can be changed by editing the properties files.
</p>
<p>
There are four properties files used:</p>
<ul>
<li>Local properties file called "SciTE.properties" which may be
present in the same directory as the file being edited.</li>
<li>Directory properties file called "SciTEDirectory.properties" which may be
present in the same or in a parent directory as the file being edited.</li>
<li>User properties file called "SciTEUser.properties" on Windows
and ".SciTEUser.properties" on GTK.</li>
<li>Global properties file called "SciTEGlobal.properties".</li>
</ul>
<p>
Settings in the local properties file override those in the directory properties file
which overrides those in the user properties file which override those
in the global properties files. Environment variables are also available as properties and these
are overridden by an explicit setting in one of the properties files.
</p>
<p>
The directory properties file can be used as project options file where user commands and
compile, build commands should work in the same manner in subdirectories of a project. The
benefit is that local properties files in subdirectories can be replaced by one properties file
which is located at the root of the project.
The evaluation of the directory properties file is disabled by default and must be enabled by
setting the variable properties.directory.enable to 1 in the user or global properties file.
</p>
<p>
The user properties file is intended for customisation by the user,
leaving the global properties file to contain the default options distributed with SciTE.
The main use of the local properties files is to change the effects of the
Compile, Build and Go commands for the files in a directory. For example, I use the javac
compiler from the Java Development Kit for most work, so SciTEGlobal.properties sets the
command for compiling .java files to "javac". If I want to use the jvc compiler for the files
in one directory, then the SciTE.properties file in that directory contains an entry setting
the command to "jvc".
</p>
<p>
The global properties file should not be edited by the user as it is replaced with
each release. Instead copy the property into the user properties file
and change it there.
</p>
<p>
On Windows, the global properties file is located in the directory of the executable.
The user properties file is looked for in the user profile directory as set in the
USERPROFILE environment variable, or in the directory of the executable if
USERPROFILE is not set.
For GTK the user properties file is found in the user's home directory and the global
properties in a directory set at build time - normally /usr/share/scite.
</p>
<p>
There are two environment variables, "SciTE_HOME" and "SciTE_USERHOME", which the user
may set to override the standard locations of the global and/or the user properties files
(this and the following applies to Windows and GTK):
</p>
<ul>
<li>If SciTE_USERHOME is set then it is where the user properties files are found.</li>
<li>If SciTE_HOME is set then it is where the global properties files are found.</li>
<li>If <b>only</b> SciTE_HOME is set then it is where both the global and user properties
files are found.</li>
</ul>
<p>
There are commands in the Options menu for opening each of the properties files.
</p>
<p>
The files are in approximately the same format as Java properties files which have a simple
text format. Lines that start with '#' or that are completely blank are comments. Other lines
are of the form
</p>
<p>
variable=value
</p>
<p>
For long values, a '\' character at the end of the line continues that value on the next line.
Space characters are significant in values but leading and trailing spaces are not significant in variable names
so "<span class="example"> x =1</span>" defines a variable called "x".
Values may include the values of other variables by using $(variablename).
</p>
<p>
The "=" function compares strings (separated by ";") and if they are the same yields "1" else "0".
To test if the value of "Status" is "2":
<span class="example">$(= $(Status);2)</span>
</p>
<p>
The "star" function may be used to collect the values of all variables that start with a particular prefix.
<span class="example">all.languages=$(star language.)</span> finds every variable
that starts with "language." and assigns that to all.languages.
This can be used to combine settings from many files for user interface elements such as the Language menu.
Within a property file level (local, directory, user, global) the ordering is alphabetically by variable name
which allows a degree of control over the ordering.
Prefixes that are used by the standard distribution are
<a href="#property-star-filter">"*filter."</a>, <a href="#property-star-language">"*language."</a>,
and <a href="#property-star-source.patterns">"*source.patterns."</a> with the
initial "*" being a convention that the variables are meant for use in a star function.
These prefixes are discussed in the <a href="#DefinedVariables">"Defined variables"</a> section.
</p>
<p>
Colours are defined like HTML with '#' followed by 6 or 8 hexadecimal digits #RRGGBB or #RRGGBBAA
defining the red, green, blue, and alpha values of the colour.
Alpha is the degree of translucency with 00 completely transparent and FF completely opaque.
A 6 digit colour is assumed to be completely opaque.
Only a few settings can currently be set translucent with an 8-digit value.
</p>
<p>
On Windows, values may be scaled using the current screen dots-per-inch so that they use more
pixels on high resolution screens and appear a reasonable size.
<span class="example">margin.width=$(scale 16)</span> makes the margin 16 pixels wide
on a normal screen and 32 pixels wide when the screen is set to 200%.
</p>
<p>
There are
some variables set by the environment to access the name of the current file as well:
</p>
<table cellpadding="0" cellspacing="0" border="1" summary="Variables set by the environment for use in property files">
<thead>
<tr><th>Name</th><th>Meaning</th></tr>
</thead>
<tr id='property-FilePath'><td>FilePath</td><td>full path of the current file</td></tr>
<tr id='property-FileDir'><td>FileDir</td><td>directory of the current file without a trailing slash</td></tr>
<tr id='property-FileName'><td>FileName</td><td>base name of the current file</td></tr>
<tr id='property-FileExt'><td>FileExt</td><td>extension of the current file</td></tr>
<tr id='property-FileNameExt'><td>FileNameExt</td><td>$(FileName).$(FileExt)</td></tr>
<tr id='property-Language'><td>Language</td><td>name of the lexer used for the current file</td></tr>
<tr id='property-SessionPath'><td>SessionPath</td><td>full path of the current session</td></tr>
<tr id='property-CurrentSelection'><td>CurrentSelection</td><td>value of the currently selected text</td></tr>
<tr id='property-CurrentWord'><td>CurrentWord</td><td>value of word which the caret is within or near</td></tr>
<tr id='property-Replacements'><td>Replacements</td><td>number of replacements made by last Replace command</td></tr>
<tr id='property-SelectionStartColumn'><td>SelectionStartColumn</td><td>column where selection starts</td></tr>
<tr id='property-SelectionStartLine'><td>SelectionStartLine</td><td>line where selection starts</td></tr>
<tr id='property-SelectionEndColumn'><td>SelectionEndColumn</td><td>column where selection ends</td></tr>
<tr id='property-SelectionEndLine'><td>SelectionEndLine</td><td>line where selection ends</td></tr>
<tr id='property-CurrentMessage'><td>CurrentMessage</td><td>most recently selected output pane message</td></tr>
<tr id='property-SciteDefaultHome'><td>SciteDefaultHome</td><td>directory in which the Global Options file is found</td></tr>
<tr id='property-SciteUserHome'><td>SciteUserHome</td><td>directory in which the User Options file is found</td></tr>
<tr id='property-SciteDirectoryHome'><td>SciteDirectoryHome</td><td>directory in which the Directory Options file is found</td></tr>
<tr id='property-APIPath'><td>APIPath</td><td>list of full paths of API files from api.<i>filepattern</i></td></tr>
<tr id='property-AbbrevPath'><td>AbbrevPath</td><td>full path of abbreviations file</td></tr>
<tr id='property-ScaleFactor'><td>ScaleFactor</td><td>the screen's scaling factor with a default value of 100</td></tr>
<tr id='property-Appearance'><td>Appearance</td><td>whether the system is using a light (0) or dark (1) theme</td></tr>
<tr id='property-Contrast'><td>Contrast</td><td>1 when the system is in high-contrast mode else 0</td></tr>
</table>
<p>
Some features use file name patterns to see which variable to use. For example, the lexer
variable can be specialised for a particular file, or a group of files based upon wildcard
matching so:<br />
<b>lexer.makefile=makefile</b> indicates that the lexer called "makefile" should be used on
files called "makefile".<br />
<b>lexer.*.cxx=cpp</b> indicates that the lexer called "cpp" should be used on files with a
"cxx" extension.<br />
Variable substitution is available on the left hand side of file pattern assignments and
look like this:<br />
<b>file.patterns.html=*.html;*.htm;*.asp;*.shtml</b><br />
<b>command.go.$(file.patterns.html)=file://$(FilePath)</b>
</p>
<p>
Wildcard matching treats '?' as matching any character and '*' as matching any number of characters, so
"*.mak" will match "proj.mak";
"Makefile*" will match "Makefile.in"; and
"*.x?l" will match "data.xml" and "transform.xsl".
</p>
<p>
Properties files are not treated as having a particular encoding, however individual property values
may be treated as having an encoding. For file names, commands, and user interface text, this is
UTF-8 so it may be easier to edit properties files as UTF-8 by inserting a coding cookie as explained later.
Other properties may be treated as byte sequences (like word.characters.<i>filepattern</i>) or in an implicit
encoding (such as keywords.<i>filepattern</i> matching the document encoding) so that it may be better to
edit these settings using a non-UTF-8 encoding. Where both UTF-8 and non-UTF-8 values are wanted,
two files can be used with different encodings and an import statement to include one in the other.
</p>
<h3 id="ImportAndConditional">
Importing properties files and conditional logic
</h3>
<p>
<a name="property-import"></a>
The 'import' statement includes a properties file as if the text were
inline at that point. The imported properties file
is either relative to the base file or absolute and a '.properties'
extension is assumed. Therefore an "import Lua" statement in
c:\os\scite\bin\SciTEGlobal.properties will import
c:\os\scite\bin\Lua.properties.
Any import statements in imported files are relative to directory of the original file,
rather than the current file.
</p>
<p>
All of the properties files in a directory can be imported with "import *".
This does not import generic properties files like user properties or abbreviations.
The set of files that are imported can be controlled with the imports.include and imports.exclude
properties.
</p>
<p>
Imported files are not scope walls: properties may be redefined in another file.
Thus, if a file contains both "import cplusplus", "import java", and "style.cpp.1=fore:$(comment.colour)" then
cplusplus.properties contains "comment.colour=#800000" and java.properties contains
"comment.colour=#008000" then the last definition wins and is active for the definitions in the base
file as well as any definitions in cplusplus.properties and java.properties.
</p>
<p>
<a name="property-if"></a>
The 'if' statement takes one argument which is a
symbol or expression that may be defined earlier in this property set file or in a base
property set. If the symbol evaluates to '0' then the test fails.
An empty string or not present symbol evaluates to 0.
An expression that evaluates to 0 or empty fails.
Into the very top property set
is inserted one of 'PLAT_GTK' with value '1',
'PLAT_WIN' with value '1', or 'PLAT_MAC' with value '1'.
For both PLAT_GTK and PLAT_MAC, 'PLAT_UNIX' is inserted with value '1'.
The system properties Appearance and Contrast are also available for use in expressions.
If the test succeeds then following indented statements are executed. When a
non-indented statement is found the if clause is finished. Only simple set
statements are allowed in if clauses. The evaluation of if statements occurs
at read time, not at evaluation time.
A reread is forced if either of the system properties changes.
<div class="example">
if PLAT_WIN<br />
caret.fore=#00FF00<br />
if $(= $(Appearance);1)<br />
caret.fore=#FFFFFF<br />
</div>
</p>
<p>
<a name="property-module"></a>
The 'module' statement is meant for use in the single-file distribution Sc1 where all of the
standard .properties files are joined together as a resource in the executable.
The module statement marks which file each segment originally came from so that the
imports.include and imports.exclude properties will work with Sc1 and unwanted properties
will not be active. The syntax is "module <name>" and the effect is to either process or
ignore all text up to the next module statement depending on whether the name is in
imports.include or imports.exclude.
</p>
<h3 id="Parameters">
Command parameters and prompting
</h3>
<p>
SciTE has 4 properties $(1) .. $(4) which can be used to run commands with
changeable parameters. To set the parameter values, use the View | Parameters
command to view the modeless Parameters dialog which shows the current values
of these parameters and allows setting new values. The accelerator keys for the main
window remain active while this dialog is displayed, so it can be used to rapidly run
a command several times with different parameters. Alternatively, a command can be
made to display the modal Parameters dialog when executed by starting the
command with a '*' which is otherwise ignored. If the modeless Parameters dialog is
already visible, then the '*' is ignored.
</p>
<h3 id="Encodings">
Encodings
</h3>
<p>
SciTE will automatically detect the encoding scheme used for Unicode files that
start with a Byte Order Mark (BOM).
The UTF-8 and UTF-16 encodings are recognised including both Little Endian and
Big Endian variants of UTF-16.
</p>
<p>
UTF-8 files will also be recognised when they contain a coding cookie on one of the
first two lines. A coding cookie looks similar to "coding: utf-8" ("coding" followed by ':'
or '=', optional whitespace, optional quote, "utf-8") and is normally contained in
a comment:</p>
<div class="example"># -*- coding: utf-8 -*-</div>
For XML there is a declaration:<br />
<div class="example"><?xml version='1.0' encoding='utf-8'?></div>
<p>
For other encodings set the code.page and character.set properties.
</p>
<h3 id="DefinedVariables">
<a name="property-"></a>
Defined variables in properties files
</h3>
<p>
Some properties are only available on
<span class="windowsonly">Windows</span>,
<span class="gtkonly">GTK</span>,
<span class="osxonly">macOS</span>, or
<span class="windows-osx">Windows & macOS</span>.
</p>
<table cellpadding="1" cellspacing="0" border="1" summary="Defined variables in property files">
<tr id='property-position.left'>
<td>
<a name='property-position.top'></a><a name='property-position.width'></a><a name='property-position.height'></a><a name='property-position.maximize'></a>
position.left<br />
position.top<br />
position.width<br />
position.height<br />
position.maximize
</td>
<td>
Set the initial window size and position. If these are omitted then the
environment's defaults are used. If the width or height are -1 or the
position.maximize property is set then the window is maximised.
</td>
</tr>
<tr class="windowsonly" id='property-position.tile'>
<td>
position.tile
</td>
<td>
If there is another copy of SciTE open, set the initial window position to be
with the left side at position.left + position.width so that most of the time
you can see both copies at once without overlap.
Works nicely if position.left set to 0 and position.width set to half of the
screen width.
</td>
</tr>
<tr id='property-buffers'>
<td>
buffers
</td>
<td>
Set to a number between 1 and 100 to configure that many buffers.
Values outside this range are clamped to be within the range.
The default is 1 which turns off UI features concerned with buffers.<br />
This value is read only once, early in the startup process and only from the
global and user properties files. So after changing it, restart SciTE to see the effect.
</td>
</tr>
<tr id='property-buffers.zorder.switching'>
<td>
buffers.zorder.switching
</td>
<td>
This setting chooses the ordering of buffer switching when Ctrl+Tab pressed.
Set to 1, the buffers are selected in the order of their previous selection otherwise
they are chosen based on the buffer number.
</td>
</tr>
<tr id='property-are.you.sure'>
<td>
<a name='property-are.you.sure.for.build'></a>
are.you.sure<br />
are.you.sure.for.build
</td>
<td>
The classic GUI question. Normally, when SciTE is about to close a file which has unsaved
edits it asks this annoying question. To turn off the question, set are.you.sure to 0 and
files will be automatically saved without bothering the user. To abandon edits to a file
use the New command. New always asks "Are you sure?" giving an opportunity to not save
the file.<br />
When running or building a file, its most likely that you want the file to be saved
first. To enable a confirmation dialog for performing Compile, Build or Go commands, set
are.you.sure.for.build=1.
</td>
</tr>
<tr id='property-save.all.for.build'>
<td>
save.all.for.build
</td>
<td>
SciTE normally saves the current buffer when performing a Compile, Build, or Go
command. To save all buffers set save.all.for.build=1
</td>
</tr>
<tr id='property-representations'>
<td>
representations
</td>
<td>
Sets up a different way of displaying particular characters.
It contains a list of items separated by ','.
An item may define the representation of a character or set an appearance or colour.
A representation item contains a character followed by '=' and its representation text.
Hexadecimal Unicode escapes may be used: '\x' followed by 2 hexadecimal digits, '\u' followed by 4, or '\U' followed by 8.
Appearance items start with '!' followed by an optional appearance number, '0' for plain or '1' for blobs,
'' for default.
Colour items start with '#' followed by 6 (opaque), 8 (translucent), or 0 (default) hexadecimal digits.
By default, representations are shown in the colour of the style of the original text.
Appearance and colour items continue to affect following representation items until they are changed or reset.
To specify the characters '\', '=', ',', '!', or '#' use an escape.
Only single characters can be represented except for the special case of Windows line ends
Carriage Return + Line Feed.<br />
The following example shows 'π' as a blob 'Pi';
'₪' as a blob 'shekel(₪)';
and with View | End of Line turned on Carriage Return + Line Feed appears as translucent red text 'crlf'.
<div class="example">
representations=π=Pi,\u20AA=shekel(\u20AA),!0,#FF000090,\x0D\x0A=crlf
</td>
</tr>
<tr id='property-view.whitespace'>
<td>
<a name='property-view.indentation.whitespace'></a>
view.whitespace<br />
view.indentation.whitespace
</td>
<td>
Setting view.whitespace to 1 makes SciTE start up with whitespace visible.<br />
Setting view.indentation.whitespace to 0 hides visible whitespace inside indentation.<br />
Setting view.indentation.whitespace to 1 makes indentation whitespace visible<br />
Setting view.indentation.whitespace to 2 makes indentation whitespace only visible
</td>
</tr>
<tr id='property-whitespace.fore'>
<td>
<a name='property-whitespace.back'></a>
whitespace.fore<br />
whitespace.back
</td>
<td>
Sets the colours used for displaying all visible whitespace, overriding any styling
applied by the lexer.
</td>
</tr>
<tr id='property-whitespace.size'>
<td>
whitespace.size<br />
</td>
<td>
Sets the size used for displaying all visible spaces, especially for when whitespace.fore
is set to be subtle.
</td>
</tr>
<tr id='property-view.indentation.guides'>
<td>
<a name='property-view.indentation.examine'></a><a name='property-highlight.indentation.guides'></a>
view.indentation.guides<br />
view.indentation.examine<br />
view.indentation.examine.<i>filepattern</i><br />
highlight.indentation.guides
</td>
<td>
Setting view.indentation.guides to 1 displays dotted vertical lines within indentation white
space every indent.size columns.<br />
Setting view.indentation.examine to 1 to display guides within real indentation whitespace only,
2 according to the next non-empty line (good for Python) or 3 according to both the next and
previous non-empty lines (good for most languages).<br />
Setting highlight.indentation.guides to 1 highlights the indentation guide associated with a
brace when that brace is highlighted.
</td>
</tr>
<tr id='property-view.eol'>
<td>
view.eol
</td>
<td>
Setting this to 1 makes SciTE display the characters that make up line ends. This looks
similar to (CR), (LF), or (CR)(LF). This is useful when using files created on another
operating system with software that is picky about line ends.
</td>
</tr>
<tr id='property-eol.mode'>
<td>
eol.mode
</td>
<td>
The default EOL mode (characters that make up line ends)
depends on your platform.
You can overwrite this behaviour by setting the property to
<div class="example">
LF for UNIX and macOS format
CR for Macintosh format prior to OS X
CRLF for DOS/Windows format
eol.auto
This setting overrides the eol.mode value and chooses the end of
line character sequence based on the current contents of the file
when it is opened. The line ending used the most in the file is chosen.
blank.margin.left
blank.margin.right
output.blank.margin.left
There is a blank margin on both sides of the text. It is drawn in the background colour
of default text. This defaults to one pixel for both left and right sides but may be
altered with these settings.
If output.blank.margin.left is set then it overrides blank.margin.left for the output pane.
margin.width
Setting this to a number makes SciTE display a selection margin to the left of the text.
The value is the number of pixels wide the selection margin should be. Line markers are
displayed in the selection margin area.
full.screen.hides.menu
Setting this to 1 hides the menu bar when the Full Screen command is used on
Windows.
On GTK the menu is always visible.
minimize.to.tray
Setting this to 1 minimizes SciTE to the system tray rather than to the task bar.
line.margin.visible
line.margin.width
SciTE is able to display a column of line numbers to the left of the selection
margin. Setting line.margin.visible to 1 makes this column visible at startup.
The line.margin.width property controls how much space is reserved for the line
numbers, in terms of the number of digits that can be displayed. To specify that
the margin should expand if needed to accommodate larger line numbers, add a '+'
after the number of digits, e.g. line.margin.width=3+.
tabbar.visible
Setting tabbar.visible to 1 makes the tab bar visible at start up.
The buffers property must be set to a value greater than 1 for this option to work.
tabbar.hide.one
Setting tabbar.hide.one to 1 hides the tab bar until there is more than one tab.
tabbar.hide.index
Setting tabbar.hide.index to 1 will hide the buffer number in tabs.
tabbar.multiline
Setting tabbar.multiline uses multiple lines for the tab bar
toolbar.visible
Setting this to 1 makes the tool bar visible at start up.
toolbar.large
Setting this to 1 makes the tool bar larger and use larger icons.
toolbar.usestockicons
SciTE has a built-in icon set for the toolbar, setting this to 1 makes
SciTE more integrated in the GNOME desktop by using the icons
provided by the current theme used in GNOME.
pathbar.visible
The path bar is a line of text under the tab bar showing the full path of the currently selected tab.
Setting pathbar.visible to 1 makes the path bar visible on GTK.
undo.redo.lazy
Setting this to 1 changes the technique used to determine when to enable or disable
tool bar buttons to be less accurate. This may improve performance on slow machines.
statusbar.visible
Setting this to 1 makes the status bar visible at start up.
statusbar.minimum.height
On macOS, when the status bar is turned off, it is still visible but only for this
height which defaults to 4 pixels. This is because of a bug that causes window corner
debris to appear in the margin when scrolling. This parameter may be set to 0
if the debris does not appear on a particular setup.
statusbar.number
statusbar.text.number
The statusbar.text.1 option defines the information displayed in the status bar
by default on all platforms.
Property values may be used in this text using the $() syntax.
Commonly used properties are: ReadOnly, EOLMode, BufferLength,
NbOfLines (in buffer), SelLength (chars), SelHeight (lines).
Extra properties defined for the status bar are LineNumber, ColumnNumber, and
OverType which is either "OVR" or "INS" depending on the overtype status.
You can also use file properties, which, unlike those above, are not updated
on each keystroke: FileName or FileNameExt, FileDate and FileTime and
FileAttr. Plus CurrentDate and CurrentTime.
On Windows only, further texts may be set as statusbar.text.2 .. and these may be
cycled between by clicking the status bar.
The statusbar.number option defines how many texts are to be cycled through.
buffered.draw
Setting this to 1 rather than the default 0 may make SciTE
draw output into a buffer bitmap first and then to the screen instead of directly to the
screen. On old platforms and some unusual modes this can result in less flickering.
but is slower.
Has no effect on macOS and may have no effect on other platforms or technology choices.
phases.draw
There are two orders in which the text area may be drawn offering a trade-off
between speed and allowing all pixels of text to be seen even when they overlap
other elements.
There may be some flickering on some platforms if buffered drawing is not turned on.
Two phase drawing (phases.draw=1)
draws all the backgrounds of a line first and then draws the text
in transparent mode. Lines are drawn separately and no line will overlap another
so any pixels that overlap into another line such as extreme ascenders and
descenders on characters will be cut off.
Multiple phase drawing (phases.draw=2)
draws the whole area multiple times, once for each feature, building up the
the appearance in layers or phases. The coloured backgrounds for all lines are
drawn before any text and then all the text is drawn in transparent mode over this
combined background without clipping text to the line boundaries. This allows
extreme ascenders and descenders to overflow into the adjacent lines.
This mode is incompatible with buffered.draw so will be treated as phases.draw=1
when buffered.draw=1.
The default is for drawing to be two phase.
Single phase drawing (phases.draw=0) is a deprecated mode that was used in previous
releases. While it can still be enabled, it is not supported and may cause incorrect drawing.
technology
On Windows Vista or newer, this can be set to 1, 2 or 3 to use the Direct2D and DirectWrite APIs
for higher quality antialiased drawing or 0 to use the older GDI. The default is 1.
The value 2 causes the frame to be retained after presentation which
may prevent drawing failures on some cards and drivers.
3 may also prevent drawing failures on some cards and drivers but with lower speed.
load.on.activate
save.on.deactivate
The load.on.activate property causes SciTE to check whether the current file has been
updated by another process whenever it is activated. This is useful when another editor
such as a WYSIWYG HTML editor, is being used in conjunction with SciTE.
The save.on.deactivate property causes SciTE to save the file whenever the SciTE
application loses focus. This is useful when developing web pages and you want to often
check the appearance of the page in a browser.
are.you.sure.on.reload
When both this and load.on.activate are set to 1, SciTE will ask if you really want to
reload the modified file, giving you the chance to keep the file as it is. By default this
property is disabled, causing SciTE to reload the file without bothering you.
save.on.timer
The save.on.timer property causes SciTE to save modified files whenever there have been no
modifications for the number of seconds specified by the property.
When set to 0, the default, this feature is disabled and files are not automatically saved.
reload.preserves.undo
When set to 1, reloading a file does not delete all the undo history. This is useful
when load.on.activate is used in conjunction with filter commands.
check.if.already.open
This option allows opening files in an existing instance of SciTE rather than
always opening a new instance.
When this option is set and SciTE is started, it checks to see if
there are any other instances of SciTE open. If there is, another
instance is asked to open the file and become active and the new
instance exits.
On Windows, the instance with the Options | Open Files Here
menu item checked opens the file.
On GTK, an arbitrary instance opens the file.
read.only
When this option is set then opened documents are initially read only.
New files are not affected by this setting.
read.only.indicator
If this option is set, SciTE indicates that the buffer is read only
by adding a "pipe"-character (|) to the file name in the tab bar and
in the buffer menu.
background.open.size
background.save.size
This setting controls whether files are opened and saved without blocking the user interface
while they are being read or written.
Files larger than the given size in bytes will be read or written in the background while
smaller files will be read or written directly and SciTE will not respond until the file access is completed.
The default value is -1 allows background processing for all files.
For saving, the size used is the in-memory size in bytes which will differ from the on-disk size
when the UTF-16 encoding is used.
file.size.large
This setting controls whether files are opened into a mode that will work with files larger
than 2 gigabytes called 'large mode'.
Files larger than the given size in bytes will be opened in large mode.
Without this setting, SciTE will use less memory but will fail for files that are
larger than 2 gigabytes when opened or grow larger than 2 gigabytes.
The default value is 100000000 so files larger than 100,000,000 bytes are opened in large mode.
The large mode only works when SciTE is built as a 64-bit application.
file.size.no.styles
Very large files take a long time to style completely and this can
make editing too slow.
Files larger than the given size in bytes will be opened with styling turned off.
It is only the file size at opening that is considered - styling will not turn on or off
when the file size changes during editing.
The default value is 1000000 so files larger than 1,000,000 bytes are opened without styling.
temp.files.sync.load
Files dropped on SciTE on Windows are normally opened asynchronously
as there may be a long list. However, files dragged from some applications
such as 7-Zip may only exist for a moment in the temporary directory and
be deleted once the drop has occurred.
Setting this to 1 makes SciTE open dropped files in the temporary directory
immediately.
quit.on.close.last
If this option is set, SciTE will close when its last buffer has been
closed, e.g. with File/Close. (By default, if this option is not set,
SciTE will remain open and will create a new blank document when its
last buffer is closed.)
highlight.current.word
When set to 1, all occurrences of the selected word are highlighted with the
colour defined by highlight.current.word.colour. By default, this option is disabled. (See indicators.alpha and indicators.under)
highlight.current.word.indicator
If set, defines the appearance of the current word highlight. This is a
structured property with multiple attributes similar to:
highlight.current.word.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80
highlight.current.word.colour
The option highlight.current.word.colour defines the colour of highlight.
The default value is #A0A000.Overridden by highlight.current.word.indicator. highlight.current.word.by.style If the option highlight.current.word.by.style is set, then only words with the same style are highlighted (e.g. if you select this word in a comment, then only occurrences of words in comments are selected). spell.ignore.filepattern Specifies a list of words that should not be treated as spelling mistakes for a particular filepattern. For example, in HTML, tag names that are not words are common so turn off the spelling highlight with:
spell.ignore.*.html=br ul toc valign blockquote kbd thead tr th tbody colspan
To turn spell checking completely off for a filepattern use the value *.
spell.mistake.indicator
If set, defines the appearance of spelling mistakes. This is a
structured property with multiple attributes similar to:
spell.mistake.indicator=style:squigglepixmap,colour:#FF0000
rectangular.selection.modifier
On GTK, the modifier key used to make rectangular selections can be set with this
property. Valid options are 2 (Ctrl), 4 (Alt) or 8 (Super). Super is often assigned to the
Windows/Start key on Windows keyboards or the Command key on Mac keyboards.
Since the Alt key is often used by window managers to move windows, this will need to be configured off to use the combination in SciTE. This can be done for Metacity using gconf-editor to modify the /apps/metacity/general/mouse_button_modifier. A valid value here is <Super>. selection.fore
selection.back Sets the colours used for displaying selected text. If one of these is not set then that attribute is not changed for the selection. The default is to show the selection by changing the background to light grey and leaving the foreground the same as when it was not selected. When selection.layer is under text (1) or over text (2), selection.back may be an 8 digit number with translucency as the last two digits. On macOS, the system's selection background may be used when selection.back is set to empty. selection.layer Sets the layer for drawing the selection background: base opaque (0), under text (1), or over text (2). selection.additional.fore
selection.additional.back Similar to selection.fore, selection.back. Sets the colours used for displaying additional selections when multiple selections are enabled or a rectangular selection is made. selection.secondary.fore
selection.secondary.back Similar to selection.fore and selection.back. Sets the colours used for displaying selections when another window holds the primary selection. selection.inactive.fore
selection.inactive.back Similar to selection.fore and selection.back. Sets the colours used for displaying selections when the window is inactive because it does not have focus. selection.always.visible Set to 1 to show the selection coloured even when SciTE is not the active application. Default is 1. caret.fore Sets the colour used for the caret. caret.additional.blinks Set whether all carets blink. 0 means only the main caret blinks. Default is 1. caret.line.back
caret.line.layer Sets the background colour and translucency used for line containing the caret. caret.line.back is the layer to draw the caret line: base opaque (0), under text (1), or over text (2). caret.line.frame This setting allows the caret line to be drawn as a rectangle inside the line instead of the whole line. It sets the width of rectanges sides. A setting of 0 returns to drawing the whole line. caret.period Sets the rate at which the caret blinks. The value is the time in milliseconds that the caret is visible before it is switched to invisible. It then stays invisible for the same period before appearing again. A value of 0 stops the caret from blinking. caret.style Sets the style of the caret. see SCI_SETCARETSTYLE for possible values. caret.width Sets the width of the caret in pixels. Only values of 1, 2, or 3 work. selection.rectangular.switch.mouse Sets whether switching to rectangular selection mode while making a selection with the mouse is allowed (1) or not (0). Default is 0. selection.multiple
selection.additional.typing
selection.multipaste Set selection.multiple to make multiple selections with the mouse by holding down the Ctrl key.
Set selection.additional.typing to 1. to allow typing, backspace and delete to affect all selections including each line of rectangular selections. When set to 0, typing only affects the main selection.
Set selection.multipaste to 1 to paste at all selections. If set to 0, the paste will only be inserted at the last selection. virtual.space Determines whether the caret can be moved into virtual space, that is, beyond the last character on a line. Set to 1 to allow virtual space when making a rectangular selection, 2 to allow the arrow keys or a mouse click to move the caret into virtual space, and 3 to allow both. 4 may be added to prevent left arrow from wrapping to previous line. caret.policy.xslop
caret.policy.width
caret.policy.xstrict
caret.policy.xeven
caret.policy.xjumps
caret.policy.yslop
caret.policy.lines
caret.policy.ystrict
caret.policy.yeven
caret.policy.yjumps
If slop is set, we can define a slop value: width for xslop, lines for yslop.
This value defines an unwanted zone (UZ) where the caret is... unwanted.
This zone is defined as a number of pixels near the vertical margins,
and as a number of lines near the horizontal margins.
By keeping the caret away from the edges, it is seen within its context,
so it is likely that the identifier that the caret is on can be completely seen,
and that the current line is seen with some of the lines following it which are
often dependent on that line.
<p>If strict is set, the policy is enforced... strictly.<br />
The caret is centred on the display if slop is not set,
and cannot go in the UZ if slop is set.</p>
<p>If jumps is set, the display is moved more energetically
so the caret can move in the same direction longer before the policy is applied again.<br />
'3UZ' notation is used to indicate three time the size of the UZ as a distance to the margin.</p>
<p>If even is not set, instead of having symmetrical UZs,
the left and bottom UZs are extended up to right and top UZs respectively.<br />
This way, we favour the displaying of useful information: the beginning of lines,
where most code reside, and the lines after the caret, e.g., the body of a function.</p>
<p>See the table below to see how these settings interact.<br />
Default: xslop, yslop, xeven, yeven=1, width=50, all others = 0.</p>
</td>
</tr>
<tr id='property-visible.policy.strict'>
<td>
<a name='property-visible.policy.slop'></a><a name='property-visible.policy.lines'></a>
visible.policy.strict<br />
visible.policy.slop<br />
visible.policy.lines
</td>
<td>
Determines how the display area is determined after a Go to command or
equivalent such as a Find or Next Message. Options are similar to caret.policy.*.
</td>
</tr>
<tr id='property-edge.mode'>
<td>
<a name='property-edge.column'></a><a name='property-edge.colour'></a>
edge.mode<br />
edge.column<br />
edge.colour<br />
</td>
<td>
Indicates long lines. The default edge.mode, 0, does not indicate long lines. An
edge.mode of 1 uses a vertical line to indicate the specified column and an edge.mode of
2 changes the background colour of characters beyond that column. For proportional fonts,
an edge.mode of 2 is more useful than 1.
</td>
</tr>
<tr id='property-control.char.symbol'>
<td>
control.char.symbol
</td>
<td>
Sets the character to use to indicate control characters. If
not set, control characters are shown as mnemonics.
</td>
</tr>
<tr id='property-error.marker.fore'>
<td>
<a name='property-error.marker.back'></a>
error.marker.fore<br />
error.marker.back
</td>
<td>
The colours used to indicate error and warning lines in both the edit and output panes
are set with these two values.
If there is a margin on a pane then a symbol is displayed in the margin to indicate
the error message for the output pane or the line causing the error message for the edit pane.
The error.marker.back is used as the fill colour of the symbol and the error.marker.fore
as the outline colour. If there is no margin then the background to the line is set to the
error.marker.back colour.
</td>
</tr>
<tr id='property-error.inline'>
<td>
<a name='property-style.error.0'></a><a name='property-style.error.1'></a><a name='property-style.error.2'></a><a name='property-style.error.3'></a>
error.inline<br />
style.error.0<br />
style.error.1<br />
style.error.2<br />
style.error.3
</td>
<td>
To see error messages interspersed with the source code, set error.inline=1.<br />
Different visual styles are used for different severities: style.error.0 is the default;
style.error.1 for warnings; style.error.2 for errors; and style.error.3 for fatal errors.
The severity of a message is inferred from finding the text "warning", "error", or "fatal" in the message.
</td>
</tr>
<tr id='property-bookmark.fore'>
<td>
<a name='property-bookmark.back'></a><a name='property-bookmark.alpha'></a><a name='property-bookmark.stroke.width'></a>
bookmark.fore<br />
bookmark.back<br />
bookmark.alpha<br />
bookmark.stroke.width
</td>
<td>
The colours used to display bookmarks in the margin. If bookmark.fore is empty then
a blue sphere is used. When the margin is turned off, bookmarks are shown by a
change in the background colour of the line with the translucency set with bookmark.alpha.<br />
The stroke width of the symbol can be set in hundredths of a pixel with bookmark.stroke.width.
When using a high DPI display or large fonts it can be worthwhile setting bookmark.stroke.width to 200.
</td>
</tr>
<tr id='property-bookmark.symbol'>
<td>
bookmark.symbol
</td>
<td>
The visual style used to display bookmarks in the margin. Set to a numeric value according to the symbols
defined in <a href="http://www.scintilla.org/ScintillaDoc.html#SCI_MARKERDEFINE">SCI_MARKERDEFINE</a>.
</td>
</tr>
<tr id='property-find.mark.indicator'>
<td>
find.mark.indicator
</td>
<td>
If set, then the Mark All command in the Find dialog will draw indicators over
each string found. This is a
<a href="#IndicatorProperty">structured property</a> with multiple attributes similar to:
<div class="example">
find.mark.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80
</div>
</td>
</tr>
<tr id='property-find.mark'>
<td>
find.mark
</td>
<td>
If set, then the Mark All command in the Find dialog will draw translucent boxes over
each string found. (See indicators.alpha and indicators.under)<br />
Overridden by find.mark.indicator.
</td>
</tr>
<tr id='property-indicators.alpha'>
<td>
indicators.alpha
</td>
<td>
This property defines the alpha level for indicators (default value is 30).
The alpha value can range from 0 (completely transparent) to 255 (no transparency).
A value out of this range is ignored and the default one is used.<br />
Will be overridden by specific indicator definitions such as find.mark.indicator.
</td>
</tr>
<tr id='property-indicators.under'>
<td>
indicators.under
</td>
<td>
If set, the indicators are drawn under text or over (by default, it is over).<br />
Will be overridden by specific indicator definitions such as find.mark.indicator.
</td>
</tr>
<tr id='property-error.select.line'>
<td>
error.select.line
</td>
<td>
When a command execution produces error messages, and you step with F4 key through
the matching source lines, this option selects the line where the error occurs.
Most useful if the error message contains the column of error too as the selection will
start at the column of the error. The error message must contain the column and must be
understood by SciTE (currently only supported for HTML Tidy). The tab size assumed by
the external tool must match the tab size of your source file for correct column reporting.
</td>
</tr>
<tr id='property-openpath'>
<td>openpath.<i>filepattern</i></td>
<td>Defines a path for the Open Selected Filename command in the File
menu. The path is searched if the selected filename doesn't contain an
absolute path or the file is not found in the document directory. The
directories in openpath are separated by ';' on Windows and ':' on macOS and GTK.<br />
An openpath setting may look like:
<div class="example">
openpath.*.txt=c:\dos\;f:\;<br />
openpath.$(file.patterns.cpp)=$(cpp_includes)</div>
</td>
</tr>
<tr id='property-open.suffix'>
<td>open.suffix.<i>filepattern</i></td>
<td>Defines a suffix to add to the selected file name for the
Open Selected Filename command in the File menu.
This is used in languages where the suffix is not given when accessing a file.
An example is python where "import xlib" will most often mean to import from
a file called "xlib.py".<br />
An open.suffix setting may look like:<br />
<div class="example">open.suffix.*.py=.py</div>
</td>
</tr>
<tr id='property-strip.trailing.spaces'>
<td>
strip.trailing.spaces<br />
strip.trailing.spaces.<i>filepattern</i>
</td>
<td>
Strips trailing white spaces from the file while saving.<br />
The global strip.trailing.spaces property can be overridden for
files that match a pattern by using the file pattern forms: <br />
<div class="example">
strip.trailing.spaces.*.yaml=0<br />
or <br />
strip.trailing.spaces.$(file.patterns.yaml)=0<br />
</div>
</td>
</tr>
<tr id='property-ensure.final.line.end'>
<td>
ensure.final.line.end
</td>
<td>
Ensures file ends with a line end when saved.
</td>
</tr>
<tr id='property-ensure.consistent.line.ends'>
<td>
ensure.consistent.line.ends
</td>
<td>
Ensures all lines end with the current Line End Characters setting when saved.
</td>
</tr>
<tr id='property-abbreviations'>
<td>
abbreviations.<i>filepattern</i>
</td>
<td>
Loads an abbreviations file for a particular language overriding the default abbreviations file.
For example,
<div class="example">
abbreviations.*.c=$(SciteUserHome)/c_abbrev.properties<br />
</div>
</td>
</tr>
<tr id='property-api'>
<td>
api.<i>filepattern</i>
</td>
<td>
Loads a set of API files for a particular language.
If there is more than one API file then the file names are separated by ';'.
API files contain a sorted list of
identifiers and function prototypes, one per line. If there are multiple files then each file should
end with a line end or the next file's first line will merge with the previous file's last line.
The "Complete Symbol" command
looks at the characters before the caret and displayed the subset of the API file
starting with that string. When an opening brace is typed, the file is searched for the
text preceding the caret and if a function prototype is found then it is displayed as a
calltip.
For example, the setting
<div class="example">
api.*.c=w.api<br />
</div>
could be used with a w.api file containing
<div class="example">
fclose(FILE* fileClose)<br />
FILE<br />
fopen(const char* szFileName, const char* szMode)<br />
fpos_t<br />
fread(void* buf, size_t size, size_t count, FILE* file)<br />
fseek(FILE* file, long lnOffset, int nOrigin)<br />
</div>
to provide autocompletion and calltips for some of the C file functions. It is best to
use the full path to the API file as otherwise the current directory is used.
See the Creating API files section for ways to create API files.
</td>
</tr>
<tr id='property-autocomplete.choose.single'>
<td>
autocomplete.choose.single
</td>
<td>
When set to 1 and an autocompletion list is invoked and there is only one element
in that list then that element is automatically chosen. This means that the matched
element is inserted and the list is not displayed.
</td>
</tr>
<tr id='property-autocomplete.*.ignorecase'>
<td>
autocomplete.<i>lexer</i>.ignorecase<br />
autocomplete.*.ignorecase
</td>
<td>
When set to 1 the API file is searched in a case insensitive way to find elements
for autocompletion lists. Otherwise matches only occur if case also matches.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-autocomplete.*.start.characters'>
<td>
autocomplete.<i>lexer</i>.start.characters<br />
autocomplete.*.start.characters
</td>
<td>
If this setting is not empty, typing any of the characters will cause
autocompletion to start. For example, if
autocomplete.python.start.characters=. and the API file for Python
contains "string.rjust" and "string.replace" then typing "string." will
cause the autocompletion to display both identifiers.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-autocomplete.*.fillups'>
<td>
autocomplete.<i>lexer</i>.fillups<br />
autocomplete.*.fillups
</td>
<td>
If this setting is not empty, typing any of the characters will cause
autocompletion to complete.
For example, if
autocomplete.python.fillups=( and the API file for Python
contains "string.replace" then typing "string.r(" will
cause "string.replace(" to be inserted.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr class="windowsonly" id='property-autocomplete.fore'>
<td>
autocomplete.fore<br />
autocomplete.back<br />
autocomplete.selected.fore<br />
autocomplete.selected.back
</td>
<td>
If these settings are not empty, they specify colours to use in
autocompletion lists.
The default values depend on the platform and system settings.
</td>
</tr>
<tr id='property-autocomplete.*.typesep'>
<td>
autocomplete.<i>lexer</i>.typesep<br />
autocomplete.*.typesep
</td>
<td>
If this setting is not empty, it specifies the character used to
separate autocompletion choices from type icon IDs.
The default value is '?'.
</td>
</tr>
<tr id='property-autocomplete.visible.item.count'>
<td>
autocomplete.visible.item.count
</td>
<td>
Set the number of items that are visible in autocompletion lists. The default is 9.
</td>
</tr>
<tr id='property-autocompleteword.automatic'>
<td>
autocompleteword.automatic
</td>
<td>
If this setting is 1 then when typing a word, if only one word in the document
starts with that string then an autocompletion list is displayed with that word so it
can be chosen by pressing Tab.
</td>
</tr>
<tr id='property-calltip.*.ignorecase'>
<td>
calltip.<i>lexer</i>.ignorecase<br />
calltip.*.ignorecase
</td>
<td>
When set to 1 the API file is searched in a case insensitive way to find the function
which will have its signature displayed as a calltip. The * form is used if there
is no lexer specific setting.
</td>
</tr>
<tr id='property-calltip.*.use.escapes'>
<td>
calltip.<i>lexer</i>.use.escapes<br />
calltip.*.use.escapes
</td>
<td>
When set to 1 the API file may contain C style backslash escapes which are listed in
the command line arguments section. The * form is used if there is no lexer specific
setting.
</td>
</tr>
<tr id='property-calltip.*.word.characters'>
<td>
calltip.<i>lexer</i>.word.characters<br />
calltip.*.word.characters
</td>
<td>
To determine the identifier to look up for calltips, a search is performed
allowing the characters in this set to be included in the identifier.
While the same setting can be used as for word.characters, sometimes
additional characters may be allowed.
For example, in Python, '.' is not normally considered part of a word
when selecting text, but it is good to allow "string.replace" to show a
calltip so calltip.python.word.characters=._$(chars.alpha) would be a
reasonable setting.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-calltip.*.parameters.start'>
<td>
<a name='property-calltip.*.parameters.end'></a><a name='property-calltip.*.parameters.separators'></a>
calltip.<i>lexer</i>.parameters.start<br />
calltip.<i>lexer</i>.parameters.end<br />
calltip.<i>lexer</i>.parameters.separators<br />
calltip.*.parameters.start<br />
calltip.*.parameters.end<br />
calltip.*.parameters.separators
</td>
<td>
Allows you to specify characters which start, end and separate
parameters. For most common languages, it's usually left brace for
start, right brace for end and comma or semicolon for separator.
E.g. CSS has colon for start, space for separator and nothing for
end. You can specify more characters for each property.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-calltip.*.end.definition'>
<td>
calltip.<i>lexer</i>.end.definition<br />
calltip.*.end.definition
</td>
<td>
API files may contain explanatory text after each function definition.
To display the explanation on a second line, set this property to the character used at the
end of the definition part. For most languages, this is ')'.
The * form is used if there is no lexer specific setting.
</td>
</tr>
<tr id='property-xml.auto.close.tags'>
<td>
xml.auto.close.tags
</td>
<td>
For XML and HTML, setting this property to 1 will automatically insert the
corresponding end tag when '>' is typed to end a start tag.
Type "<td>" and the result will be "<td></td>" with the caret
placed between the tags.
</td>
</tr>
<tr id='property-asp.default.language'>
<td>asp.default.language</td>
<td>Script in ASP code is initially assumed to be in JavaScript. To change this to VBScript set asp.default.language to 2. Python is 3.</td>
</tr>
<tr id='property-fold.abl.comment.multiline'>
<td>fold.abl.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.abl.syntax.based'>
<td>fold.abl.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.asm.comment.explicit'>
<td>fold.asm.comment.explicit</td>
<td>This option enables folding explicit fold points when using the Asm lexer. Explicit fold points allows adding extra folding by placing a ;{ comment at the start and a ;} at the end of a section that should fold.</td>
</tr>
<tr id='property-fold.asm.comment.multiline'>
<td>fold.asm.comment.multiline</td>
<td>Set this property to 1 to enable folding multi-line comments.</td>
</tr>
<tr id='property-fold.asm.explicit.anywhere'>
<td>fold.asm.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.asm.explicit.end'>
<td>fold.asm.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard ;}.</td>
</tr>
<tr id='property-fold.asm.explicit.start'>
<td>fold.asm.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard ;{.</td>
</tr>
<tr id='property-fold.asm.syntax.based'>
<td>fold.asm.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.at.else'>
<td>fold.at.else</td>
<td>This option enables C++ folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-fold.baan.inner.level'>
<td>fold.baan.inner.level</td>
<td>Set this property to 1 to enable folding of inner levels of select statements.Disabled by default. case and if statements are also eligible</td>
</tr>
<tr id='property-fold.baan.keywords.based'>
<td>fold.baan.keywords.based</td>
<td>Set this property to 0 to disable keywords based folding, which is folding based on for, if, on (case), repeat, select, while and fold ends based on endfor, endif, endcase, until, endselect, endwhile respectively.Also folds declarations which are grouped together.</td>
</tr>
<tr id='property-fold.baan.sections'>
<td>fold.baan.sections</td>
<td>Set this property to 0 to disable folding of Main Sections as well as Sub Sections.</td>
</tr>
<tr id='property-fold.baan.syntax.based'>
<td>fold.baan.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding, which is folding based on '{' & '('.</td>
</tr>
<tr id='property-fold.basic.comment.explicit'>
<td>fold.basic.comment.explicit</td>
<td>This option enables folding explicit fold points when using the Basic lexer. Explicit fold points allows adding extra folding by placing a ;{ (BB/PB) or '{ (FB) comment at the start and a ;} (BB/PB) or '} (FB) at the end of a section that should be folded.</td>
</tr>
<tr id='property-fold.basic.explicit.anywhere'>
<td>fold.basic.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.basic.explicit.end'>
<td>fold.basic.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard ;} (BB/PB) or '} (FB).</td>
</tr>
<tr id='property-fold.basic.explicit.start'>
<td>fold.basic.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard ;{ (BB/PB) or '{ (FB).</td>
</tr>
<tr id='property-fold.basic.syntax.based'>
<td>fold.basic.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.cil.comment.multiline'>
<td>fold.cil.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.comment'>
<td>fold.comment</td>
<td>This option enables folding multi-line comments and explicit fold points when using the C++ lexer. Explicit fold points allows adding extra folding by placing a //{ comment at the start and a //} at the end of a section that should fold.</td>
</tr>
<tr id='property-fold.cpp.comment.explicit'>
<td>fold.cpp.comment.explicit</td>
<td>Set this property to 0 to disable folding explicit fold points when fold.comment=1.</td>
</tr>
<tr id='property-fold.cpp.comment.multiline'>
<td>fold.cpp.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.cpp.explicit.anywhere'>
<td>fold.cpp.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.cpp.explicit.end'>
<td>fold.cpp.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard //}.</td>
</tr>
<tr id='property-fold.cpp.explicit.start'>
<td>fold.cpp.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard //{.</td>
</tr>
<tr id='property-fold.cpp.preprocessor.at.else'>
<td>fold.cpp.preprocessor.at.else</td>
<td>This option enables folding on a preprocessor #else or #endif line of an #if statement.</td>
</tr>
<tr id='property-fold.cpp.syntax.based'>
<td>fold.cpp.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.d.comment.explicit'>
<td>fold.d.comment.explicit</td>
<td>Set this property to 0 to disable folding explicit fold points when fold.comment=1.</td>
</tr>
<tr id='property-fold.d.comment.multiline'>
<td>fold.d.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.d.explicit.anywhere'>
<td>fold.d.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.d.explicit.end'>
<td>fold.d.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard //}.</td>
</tr>
<tr id='property-fold.d.explicit.start'>
<td>fold.d.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard //{.</td>
</tr>
<tr id='property-fold.d.syntax.based'>
<td>fold.d.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.dataflex.compilerlist'>
<td>fold.dataflex.compilerlist</td>
<td>Set to 1 for enabling the code folding feature in *.prn files</td>
</tr>
<tr id='property-fold.fsharp.comment.multiline'>
<td>fold.fsharp.comment.multiline</td>
<td>Setting this option to 0 disables folding of grouped line comments in F# files when fold.comment=1.</td>
</tr>
<tr id='property-fold.fsharp.comment.stream'>
<td>fold.fsharp.comment.stream</td>
<td>Setting this option to 0 disables folding of ML-style comments in F# files when fold.comment=1.</td>
</tr>
<tr id='property-fold.fsharp.imports'>
<td>fold.fsharp.imports</td>
<td>Setting this option to 0 disables folding of F# import declarations.</td>
</tr>
<tr id='property-fold.fsharp.preprocessor'>
<td>fold.fsharp.preprocessor</td>
<td>Setting this option to 1 enables folding of F# compiler directives.</td>
</tr>
<tr id='property-fold.haskell.imports'>
<td>fold.haskell.imports</td>
<td>Set to 1 to enable folding of import declarations</td>
</tr>
<tr id='property-fold.html'>
<td>fold.html</td>
<td>Folding is turned on or off for HTML and XML files with this option. The fold option must also be on for folding to occur.</td>
</tr>
<tr id='property-fold.html.preprocessor'>
<td>fold.html.preprocessor</td>
<td>Folding is turned on or off for scripts embedded in HTML files with this option. The default is on.</td>
</tr>
<tr id='property-fold.hypertext.comment'>
<td>fold.hypertext.comment</td>
<td>Allow folding for comments in scripts embedded in HTML. The default is off.</td>
</tr>
<tr id='property-fold.hypertext.heredoc'>
<td>fold.hypertext.heredoc</td>
<td>Allow folding for heredocs in scripts embedded in HTML. The default is off.</td>
</tr>
<tr id='property-fold.julia.docstring'>
<td>fold.julia.docstring</td>
<td>Fold multiline triple-doublequote strings, usually used to document a function or type above the definition.</td>
</tr>
<tr id='property-fold.julia.syntax.based'>
<td>fold.julia.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.perl.at.else'>
<td>fold.perl.at.else</td>
<td>This option enables Perl folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-fold.perl.comment.explicit'>
<td>fold.perl.comment.explicit</td>
<td>Set to 0 to disable explicit folding.</td>
</tr>
<tr id='property-fold.perl.package'>
<td>fold.perl.package</td>
<td>Set to 0 to disable folding packages when using the Perl lexer.</td>
</tr>
<tr id='property-fold.perl.pod'>
<td>fold.perl.pod</td>
<td>Set to 0 to disable folding Pod blocks when using the Perl lexer.</td>
</tr>
<tr id='property-fold.preprocessor'>
<td>fold.preprocessor</td>
<td>This option enables folding preprocessor directives when using the C++ lexer. Includes C#'s explicit #region and #endregion folding directives.</td>
</tr>
<tr id='property-fold.quotes.python'>
<td>fold.quotes.python</td>
<td>This option enables folding multi-line quoted strings when using the Python lexer.</td>
</tr>
<tr id='property-fold.raku.comment.multiline'>
<td>fold.raku.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.raku.comment.pod'>
<td>fold.raku.comment.pod</td>
<td>Set this property to 0 to disable folding POD comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.rust.comment.explicit'>
<td>fold.rust.comment.explicit</td>
<td>Set this property to 0 to disable folding explicit fold points when fold.comment=1.</td>
</tr>
<tr id='property-fold.rust.comment.multiline'>
<td>fold.rust.comment.multiline</td>
<td>Set this property to 0 to disable folding multi-line comments when fold.comment=1.</td>
</tr>
<tr id='property-fold.rust.explicit.anywhere'>
<td>fold.rust.explicit.anywhere</td>
<td>Set this property to 1 to enable explicit fold points anywhere, not just in line comments.</td>
</tr>
<tr id='property-fold.rust.explicit.end'>
<td>fold.rust.explicit.end</td>
<td>The string to use for explicit fold end points, replacing the standard //}.</td>
</tr>
<tr id='property-fold.rust.explicit.start'>
<td>fold.rust.explicit.start</td>
<td>The string to use for explicit fold start points, replacing the standard //{.</td>
</tr>
<tr id='property-fold.rust.syntax.based'>
<td>fold.rust.syntax.based</td>
<td>Set this property to 0 to disable syntax based folding.</td>
</tr>
<tr id='property-fold.sql.at.else'>
<td>fold.sql.at.else</td>
<td>This option enables SQL folding on a "ELSE" and "ELSIF" line of an IF statement.</td>
</tr>
<tr id='property-fold.verilog.flags'>
<td>fold.verilog.flags</td>
<td>This option enables folding module definitions. Typically source files contain only one module definition so this option is somewhat useless.</td>
</tr>
<tr id='property-fold.xml.at.tag.open'>
<td>fold.xml.at.tag.open</td>
<td>Enable folding for XML at the start of open tag. The default is off.</td>
</tr>
<tr id='property-html.tags.case.sensitive'>
<td>html.tags.case.sensitive</td>
<td>For XML and HTML, setting this property to 1 will make tags match in a case sensitive way which is the expected behaviour for XML and XHTML.</td>
</tr>
<tr id='property-lexer.as.comment.character'>
<td>lexer.as.comment.character</td>
<td>Overrides the default comment character (which is ';' for asm and '#' for as).</td>
</tr>
<tr id='property-lexer.asm.comment.delimiter'>
<td>lexer.asm.comment.delimiter</td>
<td>Character used for COMMENT directive's delimiter, replacing the standard "~".</td>
</tr>
<tr id='property-lexer.baan.styling.within.preprocessor'>
<td>lexer.baan.styling.within.preprocessor</td>
<td>For Baan code, determines whether all preprocessor code is styled in the preprocessor style (0, the default) or only from the initial # to the end of the command word(1).</td>
</tr>
<tr id='property-lexer.cpp.allow.dollars'>
<td>lexer.cpp.allow.dollars</td>
<td>Set to 0 to disallow the '$' character in identifiers with the cpp lexer.</td>
</tr>
<tr id='property-lexer.cpp.backquoted.strings'>
<td>lexer.cpp.backquoted.strings</td>
<td>Set to 1 to enable highlighting of back-quoted raw strings .</td>
</tr>
<tr id='property-lexer.cpp.escape.sequence'>
<td>lexer.cpp.escape.sequence</td>
<td>Set to 1 to enable highlighting of escape sequences in strings</td>
</tr>
<tr id='property-lexer.cpp.hashquoted.strings'>
<td>lexer.cpp.hashquoted.strings</td>
<td>Set to 1 to enable highlighting of hash-quoted strings.</td>
</tr>
<tr id='property-lexer.cpp.track.preprocessor'>
<td>lexer.cpp.track.preprocessor</td>
<td>Set to 1 to interpret #if/#else/#endif to grey out code that is not active.</td>
</tr>
<tr id='property-lexer.cpp.triplequoted.strings'>
<td>lexer.cpp.triplequoted.strings</td>
<td>Set to 1 to enable highlighting of triple-quoted strings.</td>
</tr>
<tr id='property-lexer.cpp.update.preprocessor'>
<td>lexer.cpp.update.preprocessor</td>
<td>Set to 1 to update preprocessor definitions when #define found.</td>
</tr>
<tr id='property-lexer.cpp.verbatim.strings.allow.escapes'>
<td>lexer.cpp.verbatim.strings.allow.escapes</td>
<td>Set to 1 to allow verbatim strings to contain escape sequences.</td>
</tr>
<tr id='property-lexer.css.hss.language'>
<td>lexer.css.hss.language</td>
<td>Set to 1 for HSS (.hss)</td>
</tr>
<tr id='property-lexer.css.less.language'>
<td>lexer.css.less.language</td>
<td>Set to 1 for Less CSS (.less)</td>
</tr>
<tr id='property-lexer.css.scss.language'>
<td>lexer.css.scss.language</td>
<td>Set to 1 for Sassy CSS (.scss)</td>
</tr>
<tr id='property-lexer.d.fold.at.else'>
<td>lexer.d.fold.at.else</td>
<td>This option enables D folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-lexer.edifact.highlight.un.all'>
<td>lexer.edifact.highlight.un.all</td>
<td>Set to 0 to highlight only UNA segments, or 1 to highlight all UNx segments.</td>
</tr>
<tr id='property-lexer.errorlist.escape.sequences'>
<td>lexer.errorlist.escape.sequences</td>
<td>Set to 1 to interpret escape sequences.</td>
</tr>
<tr id='property-lexer.errorlist.value.separate'>
<td>lexer.errorlist.value.separate</td>
<td>For lines in the output pane that are matches from Find in Files or GCC-style diagnostics, style the path and line number separately from the rest of the line with style 21 used for the rest of the line. This allows matched text to be more easily distinguished from its location.</td>
</tr>
<tr id='property-lexer.flagship.styling.within.preprocessor'>
<td>lexer.flagship.styling.within.preprocessor</td>
<td>For Harbour code, determines whether all preprocessor code is styled in the preprocessor style (0) or only from the initial # to the end of the command word(1, the default). It also determines how to present text, dump, and disabled code.</td>
</tr>
<tr id='property-lexer.haskell.allow.hash'>
<td>lexer.haskell.allow.hash</td>
<td>Set to 0 to disallow the '#' character at the end of identifiers and literals with the haskell lexer (GHC -XMagicHash extension)</td>
</tr>
<tr id='property-lexer.haskell.allow.questionmark'>
<td>lexer.haskell.allow.questionmark</td>
<td>Set to 1 to allow the '?' character at the start of identifiers with the haskell lexer (GHC & Hugs -XImplicitParams extension)</td>
</tr>
<tr id='property-lexer.haskell.allow.quotes'>
<td>lexer.haskell.allow.quotes</td>
<td>Set to 0 to disable highlighting of Template Haskell name quotations and promoted constructors (GHC -XTemplateHaskell and -XDataKinds extensions)</td>
</tr>
<tr id='property-lexer.haskell.cpp'>
<td>lexer.haskell.cpp</td>
<td>Set to 0 to disable C-preprocessor highlighting (-XCPP extension)</td>
</tr>
<tr id='property-lexer.haskell.import.safe'>
<td>lexer.haskell.import.safe</td>
<td>Set to 0 to disallow "safe" keyword in imports (GHC -XSafe, -XTrustworthy, -XUnsafe extensions)</td>
</tr>
<tr id='property-lexer.html.django'>
<td>lexer.html.django</td>
<td>Set to 1 to enable the django template language.</td>
</tr>
<tr id='property-lexer.html.mako'>
<td>lexer.html.mako</td>
<td>Set to 1 to enable the mako template language.</td>
</tr>
<tr id='property-lexer.json.allow.comments'>
<td>lexer.json.allow.comments</td>
<td>Set to 1 to enable highlighting of line/block comments in JSON</td>
</tr>
<tr id='property-lexer.json.escape.sequence'>
<td>lexer.json.escape.sequence</td>
<td>Set to 1 to enable highlighting of escape sequences in strings</td>
</tr>
<tr id='property-lexer.julia.highlight.lexerror'>
<td>lexer.julia.highlight.lexerror</td>
<td>This option enables highlighting of syntax error int character or number definition.</td>
</tr>
<tr id='property-lexer.julia.highlight.typeannotation'>
<td>lexer.julia.highlight.typeannotation</td>
<td>This option enables highlighting of the type identifier after `::`.</td>
</tr>
<tr id='property-lexer.nim.raw.strings.highlight.ident'>
<td>lexer.nim.raw.strings.highlight.ident</td>
<td>Set to 1 to enable highlighting generalized raw string identifiers. Generalized raw string identifiers are anything other than r (or R).</td>
</tr>
<tr id='property-lexer.props.allow.initial.spaces'>
<td>lexer.props.allow.initial.spaces</td>
<td>For properties files, set to 0 to style all lines that start with whitespace in the default style. This is not suitable for SciTE .properties files which use indentation for flow control but can be used for RFC2822 text where indentation is used for continuation lines.</td>
</tr>
<tr id='property-lexer.python.keywords2.no.sub.identifiers'>
<td>lexer.python.keywords2.no.sub.identifiers</td>
<td>When enabled, it will not style keywords2 items that are used as a sub-identifier. Example: when set, will not highlight "foo.open" when "open" is a keywords2 item.</td>
</tr>
<tr id='property-lexer.python.literals.binary'>
<td>lexer.python.literals.binary</td>
<td>Set to 0 to not recognise Python 3 binary and octal literals: 0b1011 0o712.</td>
</tr>
<tr id='property-lexer.python.strings.b'>
<td>lexer.python.strings.b</td>
<td>Set to 0 to not recognise Python 3 bytes literals b"x".</td>
</tr>
<tr id='property-lexer.python.strings.f'>
<td>lexer.python.strings.f</td>
<td>Set to 0 to not recognise Python 3.6 f-string literals f"var={var}".</td>
</tr>
<tr id='property-lexer.python.strings.over.newline'>
<td>lexer.python.strings.over.newline</td>
<td>Set to 1 to allow strings to span newline characters.</td>
</tr>
<tr id='property-lexer.python.strings.u'>
<td>lexer.python.strings.u</td>
<td>Set to 0 to not recognise Python Unicode literals u"x" as used before Python 3.</td>
</tr>
<tr id='property-lexer.python.unicode.identifiers'>
<td>lexer.python.unicode.identifiers</td>
<td>Set to 0 to not recognise Python 3 Unicode identifiers.</td>
</tr>
<tr id='property-lexer.rust.fold.at.else'>
<td>lexer.rust.fold.at.else</td>
<td>This option enables Rust folding on a "} else {" line of an if statement.</td>
</tr>
<tr id='property-lexer.sql.allow.dotted.word'>
<td>lexer.sql.allow.dotted.word</td>
<td>Set to 1 to colourise recognized words with dots (recommended for Oracle PL/SQL objects).</td>
</tr>
<tr id='property-lexer.sql.numbersign.comment'>
<td>lexer.sql.numbersign.comment</td>
<td>If "lexer.sql.numbersign.comment" property is set to 0 a line beginning with '#' will not be a comment.</td>
</tr>
<tr id='property-lexer.verilog.allupperkeywords'>
<td>lexer.verilog.allupperkeywords</td>
<td>Set to 1 to style identifiers that are all uppercase as documentation keyword.</td>
</tr>
<tr id='property-lexer.verilog.fold.preprocessor.else'>
<td>lexer.verilog.fold.preprocessor.else</td>
<td>This option enables folding on `else and `elsif preprocessor directives.</td>
</tr>
<tr id='property-lexer.verilog.portstyling'>
<td>lexer.verilog.portstyling</td>
<td>Set to 1 to style input, output, and inout ports differently from regular keywords.</td>
</tr>
<tr id='property-lexer.verilog.track.preprocessor'>
<td>lexer.verilog.track.preprocessor</td>
<td>Set to 1 to interpret `if/`else/`endif to grey out code that is not active.</td>
</tr>
<tr id='property-lexer.verilog.update.preprocessor'>
<td>lexer.verilog.update.preprocessor</td>
<td>Set to 1 to update preprocessor definitions when `define, `undef, or `undefineall found.</td>
</tr>
<tr id='property-lexer.xml.allow.scripts'>
<td>lexer.xml.allow.scripts</td>
<td>Set to 0 to disable scripts in XML.</td>
</tr>
<tr id='property-sql.backslash.escapes'>
<td>sql.backslash.escapes</td>
<td>Enables backslash as an escape character in SQL.</td>
</tr>
<tr id='property-styling.within.preprocessor'>
<td>styling.within.preprocessor</td>
<td>For C++ code, determines whether all preprocessor code is styled in the preprocessor style (0, the default) or only from the initial # to the end of the command word(1).</td>
</tr>
<tr id='property-tab.timmy.whinge.level'>
<td>tab.timmy.whinge.level</td>
<td>For Python code, checks whether indenting is consistent. The default, 0 turns off indentation checking, 1 checks whether each line is potentially inconsistent with the previous line, 2 checks whether any space characters occur before a tab character in the indentation, 3 checks whether any spaces are in the indentation, and 4 checks for any tab characters in the indentation. 1 is a good level to use.</td>
</tr>
<tr id='property-user.shortcuts'>
<td>
user.shortcuts
</td>
<td>
Define keys that perform commands.
This is a '|' delimited list of keys and the commands they produce.
The commands are either <a href="CommandValues.html">string or numeric IDs</a>.
Numeric IDs above 2000 are Scintilla commands and are sent to the focussed pane.
Named IDs and numeric IDs below 2000 are SciTE menu commands.<br/>
The modifiers are Ctrl, Shift, Alt, <span class="gtkonly">Super</span>, and <span class="osxonly">Control</span>.<br/>
The named keys are Left, Right, Up, Down, Insert, End, Home, Enter, Space, Tab,
KeypadPlus, KeypadMinus, KeypadMultiply, KeypadDivide, <span class="windowsonly">KeypadDecimal</span>,
Escape, Delete, PageUp, PageDown,
<span class="gtkonly">Slash</span>, <span class="gtkonly">Question</span>, <span class="gtkonly">Equal</span>,
Win, Menu.
<br/>
On macOS the command key uses the modifier Ctrl+ as this eases using one setting between platforms and
the control key uses the modifier Control+.
<br/>
The Super modifier can be used only on GTK.
<br/>
<div class="example">
user.shortcuts=<br/>
Ctrl+Shift+I|IDM_OPEN|<br/>
Ctrl+Shift+Left|IDM_CLOSE|
This property is only read at start up.
user.context.menu
Define additional commands for the context menu.
This is a '|' delimited list of menu items and the commands they
produce with commands defined as in user.shortcuts. An empty
item produces a separator.
user.context.menu=<br/>
||<br/>
Next File|IDM_NEXTFILE|<br/>
Prev File|IDM_PREVFILE|
magnificationoutput.magnification Sets the initial magnification factor of the edit and output panes. This is useful when you want to change the size of text globally, such as after changing the screen resolution without having to touch every style setting. 0 is default, negative values makes the size smaller and positive values make it larger. split.vertical
output.horizontal.size
output.vertical.size
output.initial.hide If split.vertical is set to 1 then the output pane is to the right of the editing pane, if set to 0 then the output pane is below the editing pane. The output..size settings determine the initial size of the output pane. If output.initial.hide is 1, then the output pane is hidden when SciTE first starts up even when output..size is set; otherwise the output pane is shown at startup. split.wide On GTK, the divider between the edit and output pane can be made wider by setting split.wide to 1. This makes it easier to grab with the mouse but uses up room. This property is only read at start up. clear.before.execute If set to 1 then the output pane is cleared before any tool commands are run. horizontal.scrollbar
horizontal.scroll.width
horizontal.scroll.width.tracking
output.horizontal.scrollbar
output.horizontal.scroll.width
output.horizontal.scroll.width.tracking
output.scroll
end.at.last.line If horizontal.scrollbar set to 0 then the edit pane's horizontal scrollbar is not displayed.
horizontal.scroll.width is the document width assumed for scrolling.
Similarly, output.horizontal.scrollbar and output.horizontal.scroll.width controls the horizontal scroll bar of the output pane.
The horizontal scroll bar widths can automatically grow as needed to ensure all displayed lines can be fully scrolled with horizontal.scroll.width.tracking and output.horizontal.scroll.width.tracking.
To stop the output pane from automatically scrolling, set output.scroll to 0. To have the output pane scroll and return back to the line of the executed command, set output.scroll to 1. If you want the output pane to scroll and remain at the bottom after execution, set output.scroll to 2.
The vertical scroll range is normally set so that maximum scroll position has the last line at the bottom of the view. Set end.at.last.line to 0 to allow scrolling one page below the last line. wrap
output.wrap If wrap set to 1 then the edit pane is dynamically line wrapped. If output.wrap set to 1 then the output pane is dynamically line wrapped. These options have a high performance cost which is proportional to the amount of text so should be turned off for large documents on slow machines. wrap.style Chooses between word wrapping (1, the default) and character wrapping (2). Character wrapping is a better choice for Asian languages with no spaces between words. wrap.visual.flags Flags to display markers at end and begin of wrapped lines for visual identify them. Set to 0 to not display markers (default). Set to 1 to display markers at end of wrapped lines, to 2 to display markers at begin of wrapped lines and to 3 to display markers at begin and end. wrap.visual.flags.location Flags to set the location of the display markers (if enabled) near to text or near to border. Set to 0 to have begin and end markers near to border (default). Set to 1 to have end markers near text, to 2 to have begin markers near text and to 3 to have all markers near text. wrap.indent.mode Wrapped sublines can be indented in various ways relative to the initial subline. Default mode 0 indents sublines to the left of window plus wrap.visual.startindent. Mode 1 aligns sublines to the first subline. Mode 2 aligns sublines to the first subline plus one more level of indentation. wrap.visual.startindent Sets the indention of continued wrapped lines to better visually identify the wrapping. Default is 0 (no indention). Note if wrap.visual.flags is 2 or 3 (begin marker displayed) the line is indented at least 1, even if wrap.visual.startindent is still 0. wrap.aware.home.end.keys This property changes the behaviour of the home and end keys when dynamic line wrapping is turned on. When set to 0 (the default), the Home and End keys will move the caret to the very beginning / end of the 'logical' line, whether or not the line is wrapped over multiple lines in the display. When this property is set to 1, the caret moves to the end of the current 'display' line if you press End once, or to the very end of the 'logical' line if you press End again. Likewise, the Home key moves first to the beginning of the 'display' line, then on to the very beginning of the line. In a pane where dynamic line-wrapping is not enabled, this setting has no effect. idle.styling
output.idle.styling By default (0), syntax styling is performed for all the currently visible text before displaying it. On very large files, this may make scrolling down slow. With idle.styling=1, a small amount of styling is performed before display and then further styling is performed incrementally in the background. This may result in the text initially appearing uncoloured and then, some time later, it is coloured. Text after the currently visible portion may be styled in the background with 2. To style both before and after the visible text in the background use the value 3. output.idle.styling is the equivalent setting for the output pane. cache.layout
output.cache.layout A large proportion of the time spent in the editor is used to lay out text prior to drawing it. This information often stays static between repaints so can be cached with these settings. There are four levels of caching. 0 is no caching, 1 caches the line that the caret is on, 2 caches the visible page as well as the caret, and 3 caches the whole document. The more that is cached, the greater the amount of memory used, with 3 using large amounts of memory, 7 times the size of the text in the document. However, level 3 dramatically speeds up dynamic wrapping by around 25 times on large source files so is a very good option to use when wrapping is turned on and memory is plentiful. open.filter This is a complex expression used for determining the file types that will be available in the open file dialog. For each type of file, there is some explanatory text, a '|' character, some file patterns, and another '|' character. These file types appear in the "Files of type:" pull down. The first item is the default, so you may wish to change the first item to include the file types you commonly open. The default value for this setting is built up by combining some specific settings for "All Source" and "All Files" with all the *filter settings. The "All Source" item uses a set of file patterns which combines all the *source.patterns settings.
save.filter This is a complex expression used for determining the file types that will be available in the save file dialog. The structure of the property is the same as open.filter.
Does not work on GTK. source.patterns.name Set a value to be included in the set of file extensions used for the "All Source" pull down menu item in the Open dialog when using the default value for open.filter. For example, source.patterns.ruby=.rb;.rbw; adds the file patterns *.rb and *.rbw to the set of source extensions. filter.name Set a value to be included in the file type pull down menu in the Open dialog when using the default value for open.filter. For example, filter.ruby=Ruby (rb rbw)|.rb;.rbw| adds a "Ruby" item to the file type pull down menu. Selecting that item will show files that match the patterns *.rb and .rbw. There must be 2 '|' characters in the setting. max.file.size To avoid accidentally loading huge files on slow media, or just to ensure SciTE is used only to edit human readable code, the user can set the max.file.size property to specify a limit to file loading. If unset or set to 0, there is no limit. If set to a given size in bytes and if a file to load exceeds this limit, the user is asked if the file should be loaded. If accepted, the file is read as usual. If rejected then no action is taken (no file loaded, no buffer created). save.deletes.first Causes files to be deleted before being opened for saving. Can be used to ensure saving under a different capitalisation changes the files capitalisation rather than silently using the old capitalisation. save.check.modified.time With save.check.modified.time=1, when saving and the file has been modified by another process, check if it should be overwritten by the current contents. save.session
save.recent
save.position
save.find If you set save.session, the list of currently opened buffers will be saved on exit in a session file. When you start SciTE next time (without specifying a file name on the command line) the last session will be restored automatically.
For GTK, the file is called ".SciTE.session" and is located in the directory given by the SciTE_USERHOME environment variable and if that is not set, the value of the SciTE_HOME environment variable and if that is not set, the value of the HOME environment variable and if that is not set, the top level directory.
For Windows, the file is called "SciTE.session" and is located in the directory given by the SciTE_USERHOME environment variable and if that is not set, the value of the SciTE_HOME environment variable and if that is not set, the value of the USERPROFILE environment variable and if that is not set, the directory of the SciTE executable.
Setting save.recent causes the most recently used files list to be saved on exit in the session file and read at start up.
Setting save.position causes the SciTE window position on the desktop to be saved on exit in the session file and restored at start up.
Setting save.find cause the "Find what" and "Replace with" to be saved in the session file. session.bookmarks
session.folds Setting session.bookmarks causes bookmarks to be saved in session files. If you set session.folds then the folding state will be saved in session files. When loading a session file bookmarks and/or folds are restored. Folding states are not restored if fold.on.open is set. open.dialog.in.file.directory Setting open.dialog.in.file.directory causes the open dialog to initially display the same directory as the current file. If it is not set then the system default is used. find.close.on.find Set find.close.on.find to 0, 1 or 2 to prevent (0) or allow (1) closing the the find strip automatically when the Find button is pressed. The value 2 causes the strip to close automatically only when the search finds a match which enables the user to change options or search string if a mistake was made. The default value is 1. find.replace.matchcase
find.replace.regexp
find.replace.wrap
find.replace.escapes These properties define the initial conditions for find and replace commands. The find.replace.matchcase property turns of the "Match case" option, find.replace.regexp the "Regular expression" option, find.replace.wrap the "Wrap around" option and find.replace.escapes the "Transform backslash expressions" option.
find.replacewith.focus If the find.replacewith.focus property is set, the Replace With input box is focused in the Replace dialog if Find What is non-empty. find.replace.regexp.posix Change behaviour of Regular expression search. If set to 0 (the default), characters '(' and ')' must be escaped by '' to behave as regexp meta characters. If set to 1, these characters are meta characters itself. find.replace.regexp.cpp11 Change to an alternative regular expression library provided by the C++ compiler that SciTE was built with. This may provide more features than SciTE's own regular expression code. If set to 0 (the default), SciTE's own regular expression code is used. If set to 1, the C++ regular expression library is used. find.use.strip
replace.use.strip Use in-window strips rather than dialogs for performing Find or Replace commands. find.strip.incremental
replace.strip.incremental Perform incremental search when typing in the find and replace strips. Set to 1 to enable incremental searching and 2 to enable both incremental searching and highlighting all matches. Highlighting all matches (2) can be slow on large files so should only be enabled when performance is reasonable. find.indicator.incremental Sets the indicator to use for find.strip.incremental=2 or replace.strip.incremental=2. This is a structured property with multiple attributes similar to:
find.indicator.incremental=style:compositionthick,colour:#FFB700,under
strip.button.height
Buttons on GTK often contain extra spacing that makes strips take too much room.
This setting tries to limit the height of buttons.
A value of 23 or 24 may work well.
strip.shortcuts.enable
On macOS, default behaviour is to allow use of shortcuts in the Find and Replace strips
such as ⌘W to turn "Match whole word only" on or off.
This prevents closing the file with ⌘W so shortcuts can be disabled for strips
by setting this property to 0.
This property is only read at start up.
find.replace.advanced
Enables Replace in Buffers command
and Search only in this style checkbox.
If enabled, searches can be restricted to a particular style (e.g. strings).
find.indicator
Controls the animated golden match indicator on macOS.
The default value, 1, shows and animates the find indicator then fades it away so surrounding text can be seen clearly.
Use the value 0 to disable the find indicator and the value 2 to keep the find indicator displayed.
This setting is not available on OS X 10.6.
find.commandfind.option.wholeword.0
find.option.wholeword.1
find.option.matchcase.0
find.option.matchcase.1
find.input The Find in Files command works in a similar way to the building commands executing a command line tool with output redirected to the output pane. If the command produces output understood by one of the error output passes, as does grep, then the F4 and Shift+F4 keys can be used to move through all the matches. The $(find.what), $(find.files), and $(find.directory) variables can be used for the values from the Find in Files dialog.
There are some scripts that implement this feature in Perl better than grep does itself here and here. This command line works with Cygwin on Windows, with modifications to suit the Cygwin installation directory:
find.command=cmd /c c:\cygwin\bin\find "$(find.directory)"
-name "$(find.files)" -print0 |
c:\cygwin\bin\xargs -0 fgrep -G -n "$(find.what)"
On Windows, the find string can be given to the find command through
its standard input stream to avoid problems with quote interpretation.
To do this, specify find.input to be the search string, $(find.what).
If find.command is empty then SciTE's own search code is used. This only does a simple search without regular expressions and is faster than running an external program.
When defining find.command, to specify the value of the option for the "match case" use $(find.matchcase), and to specify the value of the option "whole word" use $(find.wholeword). Additionally, you should define the properties find.option.matchcase.0, find.option.matchcase.1, find.option.wholeword.0 and find.option.wholeword.1 to match the expected parameters of the command you use for find.
find.option.wholeword.0=
find.option.wholeword.1=-w
find.option.matchcase.0=-i
find.option.matchcase.1=
find.command=cmd /c c:\cygwin\bin\find "$(find.directory)" -name "" -print0 | c:\cygwin\bin\xargs -0 grep $(find.wholeword) $(find.matchcase) -G -n "$(find.what)"
find.option.wholeword.1=-w
find.option.matchcase.0=-i
find.option.matchcase.1=
find.command=cmd /c c:\cygwin\bin\find "$(find.directory)" -name "" -print0 | c:\cygwin\bin\xargs -0 grep $(find.wholeword) $(find.matchcase) -G -n "$(find.what)"
</td>
</tr>
<tr id='property-find.files'>
<td>
find.files
</td>
<td>
This is the default set of files to search through using the Find in Files command.
The find.files property can contain a list of sets of files separated by '|' like
"*.cxx *.h|*.py *.pyw|*.html" which adds three entries to the history and
uses the first as the default value.<br />
The evaluation of this setting is a little unusual in that each entry in the value
from the property files is appended to the end of the history if that entry is
not already present. This means that opening files from different directories
will result in any local setting of find.files being added to the list.
</td>
</tr>
<tr id='property-find.in.dot'>
<td>
find.in.dot
</td>
<td>
If find.in.dot is 1 then Find in Files searches in directories that start with '.'.
The default behaviour is to prevent SciTE finding matches in the unmodified versions of
files kept by Subversion in .svn subdirectories.
</td>
</tr>
<tr id='property-find.in.binary'>
<td>
find.in.binary
</td>
<td>
If find.in.binary is 1 then Find in Files displays matches in binary files.
For Find in Files, a binary file is a file that contains a NUL byte in the first 64K block read from the file.
</td>
</tr>
<tr id='property-find.in.directory'>
<td>
find.in.directory
</td>
<td>
If set then Find in Files directory will be prefilled by this value.
If not set then Find in Files directory will be prefilled by directory of current file.
</td>
</tr>
<tr id='property-find.in.files.close.on.find'>
<td>
find.in.files.close.on.find
</td>
<td>
Set to 0 to prevent the Find in Files dialog from closing when "Find" pressed.
</td>
</tr>
<tr id='property-code.page'>
<td>
<a name='property-output.code.page'></a>
code.page<br />
output.code.page
</td>
<td>
To support a DBCS language such as Japanese, a code page can be set here. This ensures
that double byte characters are always treated as a unit so the caret is never located
between the two bytes of a double byte character.<br/><br/>
<table>
<thead><tr><th>Code page</th><th>Value</th></tr></thead>
<tr><td>Default (single byte character set)</td><td align="right">0</td></tr>
<tr><td>UTF-8</td><td align="right">65001</td></tr>
<tr><td>Japanese Shift-JIS</td><td align="right">932</td></tr>
<tr><td>Simplified Chinese GBK</td><td align="right">936</td></tr>
<tr><td>Korean Wansung</td><td align="right">949</td></tr>
<tr><td>Traditional Chinese Big5</td><td align="right">950</td></tr>
<tr><td>Korean Johab</td><td align="right">1361</td></tr>
</table>
Setting code.page to 65001 starts Unicode mode and the document is treated as
a sequence of characters expressed as UTF-8. Display is performed by converting to the
platform's normal Unicode encoding first so characters from any language will be displayed.
Correct glyphs may only be displayed if fonts are chosen that contain the appropriate glyphs.
The Tahoma font contains a wide range of glyphs so may be a good choice. <br/>
This property can <em>not</em> set a single byte character set.<br />
If output.code.page is set then it is used for the output pane which otherwise
matches the edit pane.
</td>
</tr>
<tr id='property-character.set'>
<td>
character.set
</td>
<td>
This setting allows changing the character set that is asked for when setting up fonts.
Not all of the values will work on all platforms.<br/><br/>
<table>
<thead><tr><th>Character set</th><th>Value</th></tr></thead>
<tr><td>Default</td><td align="right">0</td></tr>
<tr><td>Japanese</td><td align="right">128</td></tr>
<tr><td>Chinese GB2312</td><td align="right">134</td></tr>
<tr><td>Chinese BIG5</td><td align="right">136</td></tr>
<tr><td>Korean</td><td align="right">129</td></tr>
<tr><td>Greek</td><td align="right">161</td></tr>
<tr><td>Eastern European</td><td align="right">238</td></tr>
<tr class="windowsonly"><td>Baltic</td><td align="right">186</td></tr>
<tr class="windowsonly"><td>Turkish</td><td align="right">162</td></tr>
<tr><td>Hebrew</td><td align="right">177</td></tr>
<tr><td>Arabic</td><td align="right">178</td></tr>
<tr class="windowsonly"><td>Thai</td><td align="right">222</td></tr>
<tr class="windowsonly"><td>Vietnamese</td><td align="right">163</td></tr>
<tr class="gtkonly"><td>Cyrillic (CP866 on GTK)</td><td align="right">866</td></tr>
<tr><td>Cyrillic (CP1251 on Windows, KOI8-R on GTK)</td><td align="right">204</td></tr>
<tr class="gtkonly"><td>Cyrillic (CP1251 on GTK)</td><td align="right">1251</td></tr>
<tr class="gtkonly"><td>European with Euro (ISO 8859-15)</td><td align="right">1000</td></tr>
</table>
All of these values except for 1251 and 1000 should work on macOS or Windows.
On GTK Baltic, Turkish, Thai and Vietnamese will probably not work.
</td>
</tr>
<tr id='property-ime.interaction'>
<td>
ime.interaction
</td>
<td>
Allows a choice between windowed and inline Input Method Editors with
0 choosing windowed mode and 1 the in-line mode.
If there is no setting then a mode is chosen that may differ
between platforms and locales.
</td>
</tr>
<tr id='property-ime.autocomplete'>
<td>
ime.autocomplete
</td>
<td>
Setting 1 enables autocompletion on ime input.
To see the autocomplete box and calltip box,
autocomplete.*.start.characters and calltip.*.word.characters should be given.
Others such as calltip.parameters.* with ime characters are not supported.
It defaults to 0, so disabled.
</td>
</tr>
<tr class="windows-osx" id='property-bidirectional'>
<td>
bidirectional
</td>
<td>
Experimental and incomplete display for bidirectional languages like Arabic and Hebrew on macOS
and Windows.
Set to 1 to turn on bidirectional display.
</td>
</tr>
<tr class="gtkonly" id='property-accessibility'>
<td>
accessibility
</td>
<td>
On GTK, accessibility of the edit and output panes may be disabled by setting accessibility to 0.
Disabling accessibility may moderately improve performance and memory use.
This only affects the custom accessibility implementation, not the functionality provided by
the system such as speaking the characters typed.
It defaults to 1, so enabled.
</td>
</tr>
<tr id='property-imports.include'>
<td>
<a name='property-imports.exclude'></a>
imports.include<br />
imports.exclude
</td>
<td>
These settings control which files are imported by import statements.<br/>
The imports.include property defines the names of the properties
files that may be imported. Say you are only interested in using
fortran and lisp, then in user properties, you could set<br />
<div class="example">
imports.include=fortran lisp
The imports.exclude property is examined only if imports.include is empty or missing.
This property stops the named files from being imported.
The properties files shipped with SciTE, and which can be included or excluded with these properties, are:
abaqus ada asl asm asn1 au3 ave avs baan blitzbasic
bullant caml cmake cobol coffeescript conf cpp csound css d ecl
eiffel erlang escript flagship forth fortran freebasic gap haskell
hex html inno kix latex lisp lot lout lua matlab maxima metapost
mmixal modula3 nimrod nncrontab nsis opal oscript others
pascal perl pov powerpro powershell ps purebasic python r rebol
registry ruby rust scriptol smalltalk sorcins specman spice sql
tacl tal tcl tex txt2tags vb verilog vhdl yaml.
command.discover.properties
This property can be used to run a program to determine file encoding and other properties
when a file is loaded.
The program should print a list of property=value lines for each property it wants to set.
This is the same format as properties files.
command.discover.properties=python /home/user/FileDetect.py "$(FilePath)"
A simple Python script that recognises a particular tag that indicates the file is in the Korean code page 949:
import sys
if "Language:Korean" in open(sys.argv[1]).read():
print('code.page=949')
print('character.set=129')
comment.block.lexerif "Language:Korean" in open(sys.argv[1]).read():
print('code.page=949')
print('character.set=129')
comment.block.at.line.start.lexer
comment.stream.start.lexer
comment.stream.end.lexer
comment.box.start.lexer
comment.box.middle.lexer
comment.box.end.lexer These settings are for the comment commands in the Edit menu and are defined separately for each lexer. Not all languages support both stream and block comments.
Block comments are comments that start with a particular string and continue until the end of line. The comment.block property sets the string to be inserted or deleted at the start of the selected lines when the Block Comment or Uncomment command is performed. To make this command perform sensibly over a range of text that already contains comments and other code, the string can be defined to contain a character such as '~' that is not used in real comments.
Set comment.block.at.line.start to "1" to place block comment symbols at the start of the lines, instead of just before the first non-blank character of the lines.
Stream comments start with a particular string and end with another particular string and may continue over line ends. These are defined with comment.stream.start and comment.stream.end.
Box comments are a form of stream comment that takes several lines and uses different strings for the start, end and other lines in the range. These are defined with comment.box.start, comment.box.middle and comment.box.end. preprocessor.symbol.filepattern
preprocessor.start.filepattern
preprocessor.middle.filepattern
preprocessor.end.filepattern These settings make the preprocessor conditional movement and selection commands work. The character that defines preprocessor lines is defined by preprocessor.symbol. The preprocessor keywords that make up the start (if), middle (else), and end (endif) of preprocessor conditionals are defined by the other three properties. There may be multiple values for each of these, as, for example, C uses "if", "ifdef", and "ifndef" to begin preprocessor conditionals. lexer.filepattern A lexer splits a file up into syntactic pieces. SciTE can then display these pieces in different visual styles. Many lexers are included in SciTE for popular programming languages such as Python, Java, C/C++, JavaScript and VB. Often several file extensions (.cpp, .cc, .h) can map to one language (C++) and hence one lexer. These settings associate a file name with a lexer.
The lexers included in SciTE are written in C++ and compiled into the SciTE executable. Lexers can also be written as a Lua script or as a Lua LPeg lexer using scintillua. shbang.command On Unix, command files often have no extension and instead specify the interpreter to use for the file in an initial line that starts with "#!". When the lexer can not be otherwise determined and the file starts with "#!", the initial line is split up into words and each word is prepended with "shbang.". If a property with this name exists then it is treated as the extension of the file. For example, shbang.python=py will be triggered by an initial line #!/usr/bin/env python so the file will be treated as Python. lexilla.path Specifies a ';' separated list of dynamic lexer libraries. Each entry is a path to a dynamic library that implements the Lexilla protocol. If there is no extension then the platform standard extension '.so', '.dll', or '.dylib' is appended. The special entry '.' which is the default refers to the 'Lexilla' dynamic library distributed with SciTE. lexilla.context.contextspecific Lexer libraries may require initialisation parameters and these can be specified by prefixing the library-specific names with 'lexilla.context.'. For example, a lexer library that needs to read in XML files containing lexer definitions may require a xmllexer.directory property which is provided with lexilla.context.xmllexer.directory.
lexilla.context.xmllexer.directory=/home/example/xmllexer/definitions
keywords.filepatternkeywords2.filepattern
keywords3.filepattern
keywords4.filepattern
keywords5.filepattern
keywords6.filepattern
keywords7.filepattern
keywords8.filepattern
keywords9.filepattern
keywordclass.lexer Most of the lexers differentiate between names and keywords and use the keywords variables to do so. To avoid repeating the keyword list for each file extension, where several file extensions are used for one language, a keywordclass variable is defined in the distributed properties file although this is just a convention. Some lexers define a second set of keywords which will be displayed in a different style to the first set of keywords. This is used in the HTML lexer to display JavaScript keywords in a different style to HTML tags and attributes.
Keywords can be prefix based so ^GTK_ will treat all words that start with GTK_ as keywords. default.file.ext Defines the language mode used before the file has a name. For example, if default.file.ext=.py, then when the New command is used to create a new file then Python syntax styling is used. word.characters.filepattern Defines which characters can be parts of words. The default value here is all the alphabetic and numeric characters and the underscore which is a reasonable value for languages such as C++. whitespace.characters.filepattern Defines which characters are considered whitespace. The default value is that initially set up by Scintilla, which is space and all chars less than 0x20. Setting this property allows you to force Scintilla to consider other characters as whitespace (e.g. punctuation) during such activities as cursor navigation (ctrl+left/right). style..stylenumber
style.lexer.stylenumber The lexers determine a style number for each lexical type, such as keyword, comment or number. These settings determine the visual style to be used for each style number of each lexer.
The value of each setting is a set of ',' separated fields, some of which have a subvalue after a ':'. The fields are:
font, size, fore, back, italics, notitalics, bold,
notbold, weight, eolfilled, noteolfilled, underlined, notunderlined, case,
visible, notvisible, changeable, and notchangeable
The font field has a subvalue which is the name of
the font, the fore and back have colour subvalues,
the size field has a (fractional) numeric size subvalue,
the weight field has a numeric size subvalue (1.. 999: 100=light, 400=normal, 700=bold),
the case field has a subvalue of 'm', 'u', 'l', or 'c' for miXed, UPPER, lower, or Camel case,
and the bold, italics and eolfilled fields have no subvalue. The value
"fore:#FF0000,font:Courier,size:14" represents 14 point, red Courier text.A global style can be set up using style..stylenumber. Any style options set in the global style will be inherited by each lexer style unless overridden. style.lexer.32
style.lexer.33
style.lexer.34
style.lexer.35
style.lexer.36
style.lexer.37
style.lexer.38 As well as the styles generated by the lexer, there are other numbered styles used.
Style 32 is the default style and its features will be inherited by all other styles unless overridden.
Style 33 is used to display line numbers in the margin.
Styles 34 and 35 are used to display matching and non-matching braces respectively.
Style 36 is used for displaying control characters. This is not a full style as the foreground and background colours for control characters are determined by their lexical state rather than this style.
Style 37 is used for displaying indentation guides. Only the fore and back are used.
Style 38 is used for displaying calltips. Only the font, size, fore and back are used.
A * can be used instead of a lexer to indicate a global style setting. substyles.lexer.stylenumber Substyles are mainly used to display sets of identifiers distinctly. When working with a particular library, you may want to highlight all the calls to functions in that library differently to your own functions or operating system calls. Substyles splits one style, commonly an identifier style, into several groups. Only some lexers support this and within a lexer it will only be supported for some styles. Currently the cpp lexer allows substyles for identifiers (11) and comment doc keywords (17), and the python lexer allows substyles for identifiers (11). Language properties files will specify the styles that can be split.
This setting defines how many substyles are allocated to a particular main style. To allow 2 extra styles for identifiers in C++:
substyles.cpp.11=2
substylewords.mainstyle.substyle.filepattern
This property defines which words are to be styled in a particular substyle, in a similar way to keywords.
For example, to use the first substyle of identifiers (11) for the C++ standard library identifiers "std", "map",
"string", and "vector":
substylewords.11.1.$(file.patterns.cpp)=std map string vector
style.lexer.mainstyle.substyle
This property defines the visual appearance of a substyle.
For example, to display the first substyle of identifiers (11) as pink:
style.cpp.11.1=fore:#EE00AA
font.quality
This setting allows choosing different ways of drawing text on Windows and macOS.
The appearance will depend on platform settings and, on Windows, the technology setting.
This setting does not currently have any effect on GTK.
| Value | Meaning |
|---|---|
| 0 | Default |
| 1 | Non-antialiased |
| 2 | Antialiased |
| 3 | LCD Optimized |
braces.sloppy
style.lexer.34
style.lexer.35
braces.lexer.style Brace highlighting is a feature that shows the range of a brace when the caret is positioned immediately after it. It is especially useful when complex nested braces are used. The characters '(', ')', '[', ']', '{', and '}' are considered braces. The feature defaults to off (because it slows cursor movement) unless braces.check is set to 1. If braces.sloppy is set to 1 then if there is no brace before the caret then the character after the caret is checked. The highlighting is performed by displaying the braces in style number 34 or in style number 35 if there is no matching brace. While this is a full style, to avoid partial display of the braces, it is best to make this style differ from the standard style of braces only in foreground and background colour. Only braces with style set to braces.lexer.style (which defaults to 0) are candidates for brace match highlighting. font.monospace Defines, with the same syntax as the style properties, the font name and size to be used when the Use Monospaced Font command is performed. command.compile.filepattern
command.compile.subsystem.filepattern
command.build.filepattern
command.build.subsystem.filepattern
command.build.directory.filepattern
command.clean.filepattern
command.clean.subsystem.filepattern
command.go.filepattern
command.go.subsystem.filepattern These settings choose which commands to execute when the Compile, Build, Clean or Go menu items are selected. The subsystem options are explained in the subsystem section.
When source files are in a different directory to that they should be built in, the command.build.directory property can be set to change to a particular directory before performing the build. command.go.needs.filepattern
command.go.needs.subsystem.filepattern Sometimes a file must be compiled or built before it can be run. If this is the case, this setting indicates what command needs to be run to perform the compile or build step before running the file. When a file is compiled, this is noted and future runs will not perform a compile or build. To make a 'compile and go' Go command for .c files:
command.go..c=$(FileName)
command.go.needs..c=g++ $(FileNameExt) -o $(FileName)
command.name.number.filepatterncommand.go.needs..c=g++ $(FileNameExt) -o $(FileName)
command.number.filepattern
command.is.filter.number.filepattern
command.subsystem.number.filepattern
command.save.before.number.filepattern
command.input.number.filepattern
command.replace.selection.number.filepattern
command.quiet.number.filepattern
command.mode.number.filepattern
command.shortcut.number.filepattern Extra commands can be added to the Tools menu. For example to include the 'astyle' indenter, the properties file could contain
command.name.0..cc=Indent
command.0..cc=astyle -taO $(FileNameExt)
command.is.filter.0.*.cc=1
The first line defines the string that will appear in the Tools menu (immediately below
'Go'). The second line is the command string, similar to those of the compile, build, and
go commands. The optional command.is.filter property states that the command modifies the
current file so it may need to be read in after performing the command if
load.on.activate is set.command.0..cc=astyle -taO $(FileNameExt)
command.is.filter.0.*.cc=1
If command.save.before is set to 1, SciTE automatically saves the file before execution. If it is set to 2, SciTE will not save the file, otherwise SciTE asks you.
On Windows, the optional command.input property specifies text that will be piped
to the command. This may reference other properties; for example,
<span class="example">command.input.0.*.cc=$(CurrentSelection)</span>
would pipe the current selection to the command processes.
The command.input property is only supported for subsystem 0
(command line programs).<br />
<br />
The optional command.replace.selection can be used to specify that the
command output should replace the current selection (or be inserted at the cursor
location, if there is no selection). This property has three available settings:
0, the default, means do not replace the selection. 1 means replace the selection
when the command finishes. 2 means replace the selection only if the command
finishes with an exit code of 0. If the user cancels the command via "Tools / Stop
Executing", the selection will not be replaced even in mode 1. Note, commands run
asynchronously, so you are not prevented from modifying the document or even
switching buffers while a command is running. However, please bear in mind that
command.replace.selection will send the output to whatever window is active <i>when
the command completes</i>.<br />
A final command property is command.quiet.
A value of 1 indicates that the command I/O should not be echoed to the output pane.
This may be useful in combination with command.input and command.replace.selection.<br />
<br />
The command.mode property is a comma-separated list of flags / settings. Each mode
setting can have an argument, separated from the setting name by a colon. For
most of these, the argument portion is optional; if the setting name appears without
an argument, this works the same as "setting:yes". If a setting is included in
the command.mode but also appears as a separate command property, the mode property
will be overridden. Similarly, if a single setting appears more than once with
different arguments, the last valid argument takes priority. The supported
command.mode settings are:
<div class="example">
filter - accepts keyword arguments yes and no
quiet - accepts keyword arguments yes and no
replaceselection - accepts yes, no, and auto
savebefore - accepts yes, no, and prompt
subsystem - console, windows, shellexec, lua, director, winhelp, htmlhelp, immediate
groupundo - yes or no
The command.shortcut property allows you to specify a keyboard shortcut for the
command. By default, commands 0 to 9 have keyboard shortcuts Ctrl+0 to Ctrl+9
respectively, but this can be overridden. For commands numbered higher than 9,
there is no default keyboard shortcut. The notation used to specify keyboard
shortcuts is the same as for the user.shortcuts property, described elsewhere
in this document.<br />
<br />
If the text of a command starts with '*' then the Parameters dialog is displayed to
prompt for parameters before executing the command. The initial '*' is not included
in the command that is executed.<br />
<br />
The command number can be in the range of 0 to 49. Command numbers 0 to 9 are
assigned Ctrl+Number shortcuts. Internally these commands use IDs starting from
1100 (IDM_TOOLS) which can be used in user.shortcuts and user.context.menu as:
<div class="example">user.context.menu=Indent|1100|</div>
If command.name is empty then no item is added to the Tools menu. This can be used
for commands that are only in the context menu or user shortcuts.
</td>
</tr>
<tr id='property-command.help'>
<td>
<a name='property-command.help.subsystem'></a>
command.help.<i>filepattern</i><br />
command.help.subsystem.<i>filepattern</i>
</td>
<td>
Defines a command to be executed when the help command is
invoked or F1 pressed. On Windows, this often uses subsystem 4 as described above.
On macOS or Linux, running man or a browser are common ways of displaying help.
The word at the cursor is copied to $(CurrentWord) and this is often a good argument
to the help application. The subsystem property works in the same way as for other
commands.
</td>
</tr>
<tr id='property-command.scite.help'>
<td>
<a name='property-command.scite.help.subsystem'></a>
command.scite.help<br />
command.scite.help.subsystem
</td>
<td>
Defines a command to be executed for help on the SciTE program itself which normally
means displaying this file in a browser.
</td>
</tr>
<tr id='property-time.commands'>
<td>
time.commands
</td>
<td>
When a command is completed, print the time it took in seconds.
</td>
</tr>
<tr id='property-print.magnification'>
<td>
print.magnification
</td>
<td>
Printing is normally done with the same settings as screen display.
To make the printing larger or smaller, the print.magnification
setting is added to the size of every font when printed. To get a
good miniaturisation of text, set print.magnification to -4.
</td>
</tr>
<tr id='property-print.colour.mode'>
<td>
print.colour.mode
</td>
<td>
Some people prefer light coloured text on a black background on
screen but dark text on white on paper. If print.colour.mode is set
to 1 then each colour is inverted for printing. If set to 2 then
printing produces black text on white background. 3 forces the
background to white and 4 forces the default background to white.
</td>
</tr>
<tr class="windowsonly" id='property-print.margins'>
<td>
print.margins
</td>
<td>
Specify the default margins on the printer on Windows in left right top bottom order.
Units depends on your locale, either hundredths of millimetres or thousandths
of inches. You can see which units by the units used in the page setup dialog.
This property is only read at start up.
</td>
</tr>
<tr id='property-print.header.format'>
<td>
<a name='property-print.footer.format'></a>
print.header.format<br />
print.footer.format
</td>
<td>
These settings determine what will be printed if anything as headers and
footers. Property settings can be substituted into the values using the $(property)
syntax. There are some extra properties set up while printing:
CurrentPage, FileTime, FileDate, CurrentDate, and CurrentTime (at start of
printing).
Common properties to use in headers and footers are FileNameExt and FilePath.<br />
A header setting may look like:<br />
<div class="example">
print.header.format=$(FileNameExt) - Printed on $(CurrentDate),$(CurrentTime) - Page $(CurrentPage)
</div>
</td>
</tr>
<tr id='property-print.header.style'>
<td>
<a name='property-print.footer.style'></a>
print.header.style<br />
print.footer.style
</td>
<td>
These settings determine the style of the header and footer using the same
format as other styles in SciTE. Only the fore, back, font, size, bold, italics,
and underlined attributes are supported.
</td>
</tr>
<tr id='property-export.keep.ext'>
<td>
export.keep.ext
</td>
<td>
This property determines how the file name
(for example, LineMarker.cxx) is transformed when
exporting to include the appropriate export format extension -
.html for HTML and .rtf for RTF.
If export.keep.ext is the default, 0, then the current extension is replaced
(LineMarker.html).
If it is 1, then the export format extension is added (LineMarker.cxx.html).
If it is 2 then the final '.' is replaced by '_' and the
export format extension added (LineMarker_cxx.html).
</td>
</tr>
<tr id='property-export.html.wysiwyg'>
<td>
<a name='property-export.html.tabs'></a><a name='property-export.html.folding'></a><a name='property-export.html.styleused'></a><a name='property-export.html.title.fullpath'></a>
export.html.wysiwyg<br />
export.html.tabs<br />
export.html.folding<br />
export.html.styleused<br />
export.html.title.fullpath
</td>
<td>
When export.html.wysiwyg is set to 0 then exporting to a HTML file produces a smaller
file but which is less completely specified so may look more different to the on screen display.
When export.html.tabs is set to 1 and export.html.wysiwyg is set to 0 then tab characters in
the file are exported as tab characters rather than a sequence of space characters.<br />
The exported file can be made to fold in browsers that support CSS well (Mozilla and Internet
Explorer) by setting export.html.folding to 1.
Only export styles actually used when export.html.styleused set to 1.
The full path name of the file is put in the title, instead of just the file name
when export.html.title.fullpath set to 1.
</td>
</tr>
<tr id='property-export.rtf.wysiwyg'>
<td>
<a name='property-export.rtf.tabs'></a><a name='property-export.rtf.font.face'></a><a name='property-export.rtf.font.size'></a><a name='property-export.rtf.tabsize'></a>
export.rtf.wysiwyg<br />
export.rtf.tabs<br />
export.rtf.font.face<br />
export.rtf.font.size<br />
export.rtf.tabsize
</td>
<td>
When export.rtf.wysiwyg is set to 0 then exporting to a RTF file produces a smaller
file but which is less completely specified so may look more different to the on screen display.
When export.rtf.tabs is set to 1 and export.rtf.wysiwyg is set to 0 then tab characters in
the file are exported as tab characters rather than a sequence of space characters. <br />
export.rtf.font.face and export.rtf.font.size can be used to select a particular font and size
for the exported RTF file. export.rtf.tabsize can be set to use a different tab size than that
defined by the tabsize setting.
</td>
</tr>
<tr id='property-export.pdf.magnification'>
<td>
<a name='property-export.pdf.font'></a><a name='property-export.pdf.pagesize'></a><a name='property-export.pdf.margins'></a>
export.pdf.magnification<br />
export.pdf.font<br />
export.pdf.pagesize<br />
export.pdf.margins
</td>
<td>
export.pdf.magnification is a value that is added to the font size of the default screen style in use.
A positive value increases the PDF document's font size, and vice versa.<br />
export.pdf.font accepts a one-word parameter that selects one of the default PDF fonts: Courier,
Helvetica or Times. Helvetica is the default. Helvetica and Times do not line wrap, Courier line
wraps.<br />
export.pdf.pagesize is used to set the document's page size, using points (1/72th of an inch) as
the unit. E.g. Letter paper (8.5 inch x 11 inch) is specified using the values 612,792.<br />
export.pdf.margins sets the widths of the page margins. Margins defaults to 72 points,
or 1 inch.<br />
The PDF exporter is necessarily feature-limited because PDF is a document archival format. Supporting
a full set of features will bloat SciTE. Wrapping Helvetica or Times adequately isn't possible without
the complexities of font metrics and kerning. The PDF produced uses WinAnsiEncoding, so pre-encoding
has to be done before exporting to PDF, if you want to use extended characters.
</td>
</tr>
<tr id='property-export.tex.title.fullpath'>
<td>
export.tex.title.fullpath
</td>
<td>
The full path name of the file is put in the title, instead of just the file name
when export.tex.title.fullpath set to 1.
</td>
</tr>
<tr id='property-export.xml.collapse.spaces'>
<td>
<a name='property-export.xml.collapse.lines'></a>
export.xml.collapse.spaces<br />
export.xml.collapse.lines
</td>
<td>
export.xml.collapse.spaces and export.xml.collapse.lines are flags that control how empty lines
and runs of space characters are converted into XML. The flags are enabled if set to 1. Tab
characters are always converted by the XML exporter into spaces according to the tabsize property.
</td>
</tr>
<tr id='property-fold'>
<td>fold</td>
<td>Folding is turned on by setting fold=1.</td>
</tr>
<tr id='property-fold.symbols'>
<td>
fold.symbols
</td>
<td>
The fold.symbols setting chooses between four ways of showing folding.
Set to 0 (the default) for macOS style arrows to indicate contracted
(facing right) and expanded (facing down); 1 to display contracted folds
with "+" and expanded with "-"; 2 for a flattened tree control with round
headers and rounded joins; 3 for a flattened tree control with square headers.
</td>
</tr>
<tr id='property-fold.fore'>
<td>
<a name='property-fold.back'></a>
fold.fore<br />
fold.back
</td>
<td>
Sets the colours used for folds. fold.fore sets the outline colour, fold.back sets the fill.
An 8-digit value sets the translucency as well: #FF00007F is half-transparent red.
</td>
</tr>
<tr id='property-fold.stroke.width'>
<td>
fold.stroke.width
</td>
<td>
Sets the stroke width of the fold symbols in hundredths of a pixel.
The default value, 100 is good for standard displays but 200 may be better for high DPI displays,
</td>
</tr>
</tr>
<tr id='property-fold.margin.width'>
<td>
fold.margin.width
</td>
<td>
Sets the width of the fold margin.
</td>
</tr>
<tr id='property-fold.margin.colour'>
<td>
<a name='property-fold.margin.highlight.colour'></a>
fold.margin.colour<br />
fold.margin.highlight.colour
</td>
<td>
These two properties defined the fold margin colour and fold
margin highlight colour. If they are not defined (left commented out) the colours for the
fold margin will default to a reasonable pair of colours.
On Windows, the system colours are used to make the fold margin appear like the background
of scroll bars. As an example, with <span class="example">fold.margin.colour=#FF0000</span> and
<span class="example">fold.margin.highlight.colour=#0000FF</span>, the fold margin is a mixture of red
and blue.
</td>
</tr>
<tr id='property-fold.on.open'>
<td>
fold.on.open
</td>
<td>
To automatically fold files as much as possible when loaded, set
fold.on.open to 1.
</td>
</tr>
<tr id='property-fold.flags'>
<td>
fold.flags
</td>
<td>
Not really documented ;) bit flags which may go away.
2, 4, 8, and 16 control drawing lines above and below folding lines if
expanded or not expanded.
Set to 64 to help debug folding by showing hexadecimal fold levels in margin.
</td>
</tr>
<tr id='property-fold.compact'>
<td>
fold.compact<br />
</td>
<td>
For HTML, XML, Lua and C++ and similar files, turning this option on leads to blank lines following the
end of an element folding with that element. Defaults to on.
</td>
</tr>
<tr id='property-fold.highlight'>
<td>
fold.highlight<br />
</td>
<td>
Set to 1 to enable highlight for current folding block (smallest one that contains the caret).
By default, it's disable. Note : The highlight is enabled only when fold.symbols equals
to 2 (round headers) or 3 (square headers).
</td>
</tr>
<tr id='property-fold.highlight.colour'>
<td>
fold.highlight.colour<br />
</td>
<td>
Define the colour of highlight. The colour by default is red (#FF0000).
An 8-digit value sets the translucency as well.
</td>
</tr>
<tr id='property-title.full.path'>
<td>
title.full.path
</td>
<td>
Chooses how the file name is displayed in the title bar.
When 0 (default) the file name is displayed. When 1 the full path is displayed.
When 2 the window title displays "filename in directory".
</td>
</tr>
<tr id='property-title.show.buffers'>
<td>
title.show.buffers
</td>
<td>
When set to 1 shows the current buffer number in the title bar.
</td>
</tr>
<tr id='property-tabsize'>
<td>
<a name='property-tab.size'></a><a name='property-indent.size'></a><a name='property-use.tabs'></a><a name='property-indent.auto'></a><a name='property-tab.indents'></a><a name='property-backspace.unindents'></a>
tabsize<br />
tab.size.<i>filepattern</i><br />
indent.size<br />
indent.size.<i>filepattern</i><br />
use.tabs<br />
use.tabs.<i>filepattern</i><br />
indent.auto<br />
tab.indents<br />
backspace.unindents
</td>
<td>
Sets the size of a tab as a multiple of the size of a space character in the style of the
default style definition. The indent size is the size to use when performing automatic
indentation and may be different from the tab size. Many people use a tab size of 8 but
4 character indentation. When creating indentation, use.tabs determines whether the
indentation is made up purely from space characters or from a mix of tabs and spaces
using as many tabs as possible. <br />
The global tabsize, indent.size, and use.tabs properties can be overridden for
files that match a pattern by using the file pattern forms: <br />
<div class="example">
indent.size.*.pas=3</div>
If indent.auto is set then indent.size and use.tabs are set according to the contents
of the opened document.<br />
The properties file settings apply to newly opened files but remain constant once the file is open
unless changed using the Change Indentation Settings dialog.<br />
If tab.indents is set then pressing tab within indentation whitespace indents by indent.size
rather than inserting a tab character. If backspace.unindents then pressing backspace
within indentation whitespace unindents by indent.size rather than deleting the character
before the caret.
</td>
</tr>
<tr id='property-indent.automatic'>
<td>
<a name='property-indent.opening'></a><a name='property-indent.closing'></a><a name='property-indent.maintain'></a>
indent.automatic<br />
indent.opening<br />
indent.closing<br />
indent.maintain.<i>filepattern</i>
</td>
<td>
Determines the look of automatic indentation. Automatic indentation is turned on with
indent.automatic=1. To indent a brace line after a compound statement start set
indent.opening=1, likewise for the terminating brace. So with both set to 0:
<div class="example">
if (c)<br />
{<br />
s;<br />
}<br />
</div>
And with both set to 1:
<div class="example">
if (c)<br />
{<br />
s;<br />
}<br />
</div>
Automatic indentation may be changed to simply repeat the indentation of the
previous line for some files with indent.maintain.<i>filepattern</i>=1 which
overrides the other language specific settings.
</td>
</tr>
<tr id='property-statement.indent'>
<td>
<a name='property-statement.end'></a><a name='property-statement.lookback'></a><a name='property-block.start'></a><a name='property-block.end'></a>
statement.indent.<i>filepattern</i><br />
statement.end.<i>filepattern</i><br />
statement.lookback.<i>filepattern</i><br />
block.start.<i>filepattern</i><br />
block.end.<i>filepattern</i>
</td>
<td>
Each of these settings starts with a style number and then a set of words or characters
that define how to recognise that feature. If there is a second space in the setting then
it is a set of words, otherwise a set of characters. The set of keywords used to indicate
the start of a compound statement is defined in statement.indent. For example:
<div class="example">
statement.indent.$(file.patterns.cpp)=5 if else while
</div>
says that for C++ the words "if", "else", and "while" in keyword style, 5, start compound
statements which leads to the next line being indented if no other factors affect it. However,
if a statement end is found on the same line then the next line is not indented. For C++ the
statement end is the semicolon in the operator style, so this is defined:
<div class="example">
statement.end.$(file.patterns.cpp)=10 ;
</div>
The number of lines looked at to determine indentation can be set with statement.lookback.
This can be used either to bound the amount of time spent on this task or to specify
that only the last line be examined for indentation.<br />
The block.start and block.end properties define the language elements used to bracket groups
of statements. In C++ these are '{' and '}'.
</td>
</tr>
<tr id='property-indent.python.colon'>
<td>
indent.python.colon
</td>
<td>
For Python, automatically indent by one level if the previous line ended in a ':'
ignoring comments and whitespace. Otherwise use the same indentation as the previous line.
This property overrides other indentation settings.
</td>
</tr>
<tr id='property-os.x.home.end.keys'>
<td>
os.x.home.end.keys
</td>
<td>
Chooses the standard macOS behaviour for the Home and End keys which is
to scroll the file to the start or end. This setting takes precedence over
vc.home.key.
</td>
</tr>
<tr id='property-vc.home.key'>
<td>
vc.home.key
</td>
<td>
Chooses the behaviour of the Home and Shift+Home keys. 1, the default is like
Visual C++ moving the caret to the end of the line indentation unless already
there, in which case it moves to the start of the line. 0 moves to the start of the line.
</td>
</tr>
<tr class="windowsonly" id='property-warning.findwrapped'>
<td>
<a name='property-warning.notfound'></a><a name='property-warning.wrongfile'></a><a name='property-warning.executeok'></a><a name='property-warning.executeko'></a><a name='property-warning.nootherbookmark'></a>
warning.findwrapped<br />
warning.notfound<br />
warning.wrongfile<br />
warning.executeok<br />
warning.executeko<br />
warning.nootherbookmark
</td>
<td>
Allows for sounds to be played and the window to be flashed
on Windows when particular events occur.
The values consist of three items separated by ',': flash duration, sound
and sound duration. If sound is a number then it is treated as a pitch and
played for the duration in milliseconds.
Otherwise it is treated as a path to a sound file
that is played. If you do not want a flash, specify 0 for flash duration.
For example,
<div class="example">
warning.wrongfile=0,C:\Windows\Media\SFX\Glass.wav
</div>
will play the glass sound if open selected is given a bad file name.
The findwrapped warning occurs when a find operation wraps past
either end of the file,
notfound when the find or preprocessor conditional move commands
fail to find a match,
executeok when a command such as build
executes successfully, executeko when a command fails, and
nootherbookmark when there is no bookmark to find.
</td>
</tr>
<tr class="gtkonly" id='property-fileselector.width'>
<td>
<a name='property-fileselector.height'></a>
fileselector.width<br />
fileselector.height
</td>
<td>
For the GTK version determines the initial size of the file
selector dialog invoked by the Open and Save commands.
Setting has no effect on Windows.
</td>
</tr>
<tr id='property-fileselector.show.hidden' class="osxonly">
<td>
fileselector.show.hidden
</td>
<td>
On macOS setting this to 0 makes the file selector dialog
invoked by the Open command not show hidden files.
</td>
</tr>
<tr id='property-locale.properties'>
<td>
locale.properties
</td>
<td>
Set the name of the localisation file. For a multi-user installation
this allows each user to set a preferred user interface language.<br />
On macOS, localisation files for some languages are installed in the translations
subdirectory of the user home directory which allows setting
the user interface to, for example, German with
<div class="example">
locale.properties=$(SciteUserHome)/translations/locale.de.properties
</div>
</td>
</tr>
<tr id='property-translation.missing'>
<td>
translation.missing
</td>
<td>
When using a localised version, if a term is not found in the locale.properties
translation file then use the value of translation.missing instead. By setting
this to a marker such as "***" it is easier to check where terms have not been
provided with translations.
</td>
</tr>
<tr id='property-menu.language'>
<td>
menu.language
</td>
<td>
Defines the entries in the Language menu and the file extensions they map to.
Each menu item is defined by 3 elements, language name, extension and an optional
keyboard equivalent. Each element is terminated by '|'. For example:<br />
<span class="example">H&ypertext|html|F12|</span><br />
Menu items may be commented out by prefixing the name with '#'.
The default value for this setting is built up by combining all
<a href="#property-star-language">*language</a> settings.<br />
This value is read only once when starting SciTE, so, after changing it,
restart SciTE to see the effect.
</td>
</tr>
<tr id='property-star-language'>
<td>
*language.<i>name</i>
</td>
<td>
Set a value to be included in the Language menu when using the default value for
<a href="#property-menu.language">menu.language</a>.
For example, <span class="example">*language.ruby=Ruby|rb|F9|</span> adds a "Ruby"
item to the Language menu which maps to the "rb" file extension and can be chosen with the F9 key.
More than one language may be defined in one variable.
There must be a multiple of 3 '|' characters in the setting.
</td>
</tr>
<tr class="gtkonly" id='property-menukey.*'>
<td>
menukey.*
</td>
<td>
The menukey.* settings allow the user to redefine accelerator keys for menus
without having to resort to modifying the SciTE source code. The syntax for the setting is:
<div class="example">
menukey.menu_title.menu_name=<modifier>key
</div>
For example, the File | Exit command accelerator could be specified as follows:
<div class="example">
menukey.file.exit=<control>Q
</div>
Note that spaces in menu titles and names must be converted to underscores,
and trailing ellipses removed. For example, "File | Save As...." is referenced as "menukey.file.save_as".
<br /><br />
Multiple modifiers may be specified, though each must be surrounded by angle brackets. The
recognised modifiers are the same as for the user.shortcuts setting described above. The recognised named
keys are also the same as for user.shortcuts, with the addition of "none" to indicate that no accelerator
key should be defined for a particular menu.
</td>
</tr>
<tr class="windowsonly" id='property-source.default.extensions'>
<td>
source.default.extensions
</td>
<td>
If the name specified on the command line cannot be found as a directory or file - including a wild-card
search, the contents of the property are treated as default extensions to be used to locate the file name.<br />
An example is: .cxx|.cpp|.c|.hxx|.hpp|.h|.bat|.txt|.lua<br />
Attempting to open win32\SciTEWin would open win32\SciTEWin.cxx since it matches before win32\SciTEWin.h
<br />
If the property contains an entry such as Bar.cxx|.cxx and you attempt to open win32\SciTEWin, it will open
ScTEWinBar.cxx since that is the first match.
</td>
</tr>
<tr id='property-ext.lua.startup.script'>
<td>
<a name='property-ext.lua.auto.reload'></a><a name='property-ext.lua.reset'></a><a name='property-extension'></a>
ext.lua.startup.script<br />
ext.lua.auto.reload<br />
ext.lua.reset<br />
extension.<i>filepattern</i>
</td>
<td>
The ext.lua properties are specific to the <a href="SciTELua.html">
SciTE Lua Scripting Extension</a>. The extension.<i>filepattern</i> property
is part of the generic <a href="SciTEExtension.html">SciTE Extension
Interface</a> but is currently only used by the Lua Scripting Extension.
<br />
The ext.lua.startup.script property defines the filename of a Lua script that
will be loaded when SciTE starts to set up the global state for Lua.
The default value is $(SciteUserHome)/SciTEStartup.lua.
You should use an absolute path for this property, but can reference the
$(SciteDefaultHome) or $(SciteUserHome) properties. Global event handlers,
command functions, as well as other functions and objects can be defined here.
<br />
The ext.lua.auto.reload property determines what happens if you save the
startup script, or the active extension script, from within SciTE. If it
is set to 0, the startup script only applied at startup time
or when you switch buffers (depending on ext.lua.reset), and changes to the
extension script are only applied when you switch buffers. If
ext.lua.auto.reload is set to 1 (the default), SciTE will re-initialize the global scope
immediately when either script is saved from within SciTE. <i>Even
when ext.lua.auto.reload is enabled, SciTE will not notice if the files
are changed from outside the current SciTE instance. For that, see
ext.lua.reset below.</i>
<br />
The ext.lua.reset property is primarily for debugging. If ext.lua.reset
is 0 (the default), the startup script property is checked only once -
when SciTE starts. If ext.lua.reset is changed to 1, SciTE will check
the startup script property, and reload the new startup script, each
time you switch buffers. As such, it has a different (larger) set of
side effects than ext.lua.auto.reload. In some situations it will make
sense for both auto.reload and reset to be enabled, but usually
ext.lua.auto.reload alone will suffice.
<br />
Aside from ext.lua.startup.script, the extension.<i>filepattern</i> property
provides a way to load additional functions and event handlers that may be
specific to a given file type. If the extension property value ends in .lua
and names a file that exists, the Lua extension evaluates the script so that event
handlers and commands defined in the script are available while that buffer
is active. Functions and objects defined through ext.lua.startup.script are
still accessible, unless they are overridden.
<br />
The extension property can also define behaviour that is specific to a given
directory. If a bare filename (no path) is specified in the extension
property, SciTE looks for the file in the standard property file locations,
starting with the local directory. This can be very useful in combination
with a local SciTE.properties file.
</td>
</tr>
<tr class="windowsonly" id='property-create.hidden.console'>
<td>
create.hidden.console
</td>
<td>
On Windows, to prevent a console window appearing momentarily whenever the Lua
os.execute or io.popen functions are called to execute programs, set create.hidden.console to 1.
This property is only read at startup so changing behaviour requires restarting SciTE.
</td>
</tr>
<tr id='property-caret.sticky'>
<td>
caret.sticky
</td>
<td>
Controls when the last position of the caret on the line is modified.
When set to 1, the position is not modified when you type a character, a tab,
paste the clipboard content or press backspace. The default is 0 which turns
off this feature.
</td>
</tr>
<tr id='property-properties.directory.enable'>
<td>
properties.directory.enable
</td>
<td>
Enables or disables the evaluation of the directory properties file.
The default is 0 which disables the evaluation. Any other value enables
this properties file.
</td>
</tr>
<tr id='property-editor.config.enable'>
<td>
editor.config.enable
</td>
<td>
Enables or disables the reading and evaluation of .editorconfig files that follow the
<a href="http://editorconfig.org/">EditorConfig</a> definition.
The default is 0 which disables the evaluation with any other value enabling it.
</td>
</tr>
<tr id='property-save.path.suggestion'>
<td>
save.path.suggestion
</td>
<td>
If set, SciTE suggests this name and directory when we perform the "Save" command for a new, unnamed buffer.
The directory should exist. (This setting doesn't affect the "Save As" command).
A save.path.suggestion setting may be defined as either a relative to $(SciteUserHome) path, like:
<div class="example">
save.path.suggestion=$(SciteUserHome)\Notes\note_$(TimeStamp).txt<br/>
</div>
or as a full path. It accepts both directory delimiters: the slash "/" and the backslash "\".<br/>
If $(TimeStamp) is specified, it will be replaced by an actual timestamp, 14 characters long.
</td>
</tr>
</table>
<p>
caret.policy.{x|y}<param> interaction:
</p>
<table cellpadding="1" cellspacing="0" border="1" summary="Caret policy">
<tr>
<th>slop</th>
<th>strict</th>
<th>jumps</th>
<th>even</th>
<th>Caret can go to the margin</th>
<th>When reaching limit<br />
(going out of visibility or<br />
going into the UZ)<br />
display is...</th>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret on top/on right</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td>Yes</td>
<td>moved by one position</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret on top/on right</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">1</td>
<td>Yes</td>
<td>centred on the caret</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">-</td>
<td align="center">0</td>
<td>Caret is always on top/on right of display</td>
<td>-</td>
</tr>
<tr>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">-</td>
<td align="center">1</td>
<td>No, caret is always centred</td>
<td>-</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret out of the asymmetrical UZ</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">1</td>
<td>Yes</td>
<td>moved to put caret out of the UZ</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">0</td>
<td>Yes</td>
<td>moved to put caret at 3UZ of the top or right margin</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">1</td>
<td align="center">1</td>
<td>Yes</td>
<td>moved to put caret at 3UZ of the margin</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">-</td>
<td align="center">0</td>
<td>Caret is always at UZ of top/right margin</td>
<td>-</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">0</td>
<td align="center">1</td>
<td>No, kept out of UZ</td>
<td>moved by one position</td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">1</td>
<td align="center">0</td>
<td>No, kept out of UZ</td>
<td>moved to put caret at 3UZ of the margin</td>
</tr>
</table>
<h3 id="IndicatorProperty">
Indicator definition
</h3>
<p>Properties that define indicators look like</p>
<div class="example">
highlight.current.word.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80</div>
<p>The structure uses commas between attributes and a colon between an attribute name and value:</p>
<table cellpadding="1" cellspacing="0" border="1" summary="Caret policy">
<tr>
<th>attribute</th>
<th>value</th>
<th>default</th>
</tr>
<tr>
<td>style</td>
<td>one of plain, squiggle, tt, diagonal, strike, hidden, box, roundbox, straightbox, fullbox, dash,
dots, squigglelow, dotbox, squigglepixmap, compositionthick, compositionthin,
textfore, gradient, gradientcentre, point, or pointcharacter.<br />
</td>
<td>plain</td>
</tr>
<tr>
<td>colour or color</td>
<td>a hex colour value preceded by '#' such as #008020.</td>
<td>black</td>
</tr>
<tr>
<td>fillalpha</td>
<td>the translucency from 0 for completely transparent to 255 for opaque of the fill for roundbox, straightbox and dotbox.</td>
<td>30</td>
</tr>
<tr>
<td>outlinealpha</td>
<td>the translucency from 0 for completely transparent to 255 for opaque of the outline for roundbox, straightbox and dotbox.</td>
<td>50</td>
</tr>
<tr>
<td>under</td>
<td>the indicator is drawn under the text.</td>
<td>no</td>
</tr>
<tr>
<td>notunder</td>
<td>the indicator is drawn over the text.</td>
<td>yes</td>
</tr>
</table>
</p>
<p>Samples:<br />
<img src="SciTEIndicators.png" alt="Indicator samples" /></p>
<h3 id="NewLanguage">
Supporting a new language
</h3>
<p>
For languages very similar to existing supported languages, which may only differ in a minor
feature such as the keywords used, the existing lexers can often be reused. The set of
keywords can then be changed to suit the new language. Java and JavaScript could have
reasonably reused the C++ lexer. The Java lexer was added only to support doc comments.
</p>
<p>
For languages that can not be lexed with the existing lexers, a new lexer can be coded in
C++. These can either be built into Lexilla, or put into an
external module and loaded when SciTE runs.
See Lexilla and the <a href="#property-lexillapath">lexilla.path</a> property.
</p>
<p>
The open.filter should be modified to include the file extensions used for the new language
and entries added for command.compile, command.build, command.go and command.go.needs for the
language.
</p>
<h3 id="APIFiles">
Creating API files
</h3>
<p>
The .api files can be generated by hand or by using a program.
There are also <a href="http://code.google.com/p/scite-files/wiki/Customization">downloadable ready-to-use
.api files.</a>
</p>
<p>
For C/C++ headers, an API file can be generated using
<a href="http://ctags.sourceforge.net/">ctags</a>
and then the <a href="tags2api.py">
tags2api Python script</a> (which assumes C/C++ source) on the tags file to grab complete
multiple line function prototypes.
Some common headers surround parameter lists with a __P macro and may have
comments. The <a href="cleanapi.cc">cleanapi</a> utility may be used on these files.
</p>
<p>
To generate an API file for Python modules, there is a
<a href="gen_python_api.zip">gen_python script</a>.
</p>
<p>
To generate an API file for Java classes, there is a
<a href="ApiBuilder.java">ApiBuilder.java</a> program.
</p>
<h3 id="OpenSelected">
Open Selected Filename
</h3>
<p>
This command opens the file for the file name selected in either the edit or output pane.
It uses the current selection or searches around the caret to try to
find a file name based on which characters are normally used in a path.
If there is no extension then an extension may be inferred from the current file using the
open.suffix property which defaults to .properties in a .properties file.
If the file name is followed by a number (in a format similar to ctags, grep output,
or Visual Studio messages) then that line is displayed in the opened file.
If the file name is an absolute path then it is opened directly otherwise it is looked for
in the current directory and then in the directory specified by the openpath property.
On Windows, web, ftp, mail and news URLs are handled by opening their
associated application.
</p>
<h3 id="Translations">
SciTE in other languages
</h3>
<p>
SciTE can be and has been <a href="http://code.google.com/p/scite-files/wiki/Translations">translated into other languages</a>.
</p>
<h3 id="Building">
Building SciTE
</h3>
<p>
The procedure for building and installing SciTE is described in the README file in the scite
directory.
</p>
<h3 id="Extending">
Extending SciTE
</h3>
<p>
There are two formal extension interfaces for SciTE, the
<a href="SciTEExtension.html">SciTE Extension Interface</a>
is for extending SciTE with code compiled into the SciTE executable and the
<a href="SciTEDirector.html">SciTE Director Interface</a> is for
manipulating SciTE on Windows from another application.
</p>