SciTE Standard Editing 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.
Bionicspider Online Solutions is located in Victoria, British Columbia and specializes in web, computer, and network solutions for small and medium businesses. More discussions. Cheat giveitem 'Blueprint'/Game/Mods/TekStructures/BionicSpider/PrimalItemTekSpider.PrimalItemTekSpider' 1 0 0. Our expertise is in obtaining permits and regulatory approvals for. Website Development And Hosting By: Bionicspider Online Solutions Evolve Your Web.
BionicSpider (BionicSpider.exe). Bionicspider, the most powerful Window Organizing application, brings order to your chaotic desktop. Create multiple groups to.
SciTE can perform commands to compile or run source files with the output from these commands directed into the output pane. For example, if 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. 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: print ( 'hi' ) mistake Perform the Tools| Go command. The results should look like: >pythonw -u printhi.py hi Traceback (most recent call last): File 'printhi.py', line 2, in mistake NameError: name 'mistake' is not defined >Exit code: 1 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: 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 '.' If command execution has failed and is taking too long to complete then the Tools| Stop Executing command can be used.
Command subsystem 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.
Windows 0 console Command line programs Do not use for GUI programs as their windows will not be visible. 1 windows Programs that create their own windows 2 shellexec Run using ShellExecute A good way to open HTML files and similar as it handles this similarly to a user opening the file from the shell. 3 lua director Internal extension or director extension 4 htmlhelp Open in HtmlHelp program Two part command separated! With the first part being the topic to search for and the second the name of the help file 5 winhelp Open with WinHelp function Two part command similar to subsystem 4 7 immediate Internal script that is executed immediately instead of being queued. GTK+ and macOS 0 console Execute tool and wait for it to finish 2 shellexec Execute in background 3 lua director Internal extension or director extension 7 immediate Internal script that is executed immediately instead of being queued.
Command line arguments 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. For Windows: 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 ('--')) The command line argument '-@' (without the quotes) is special in that file names are read from stdin and opened. Note: 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. Note: If stdin is not redirected, these arguments are effectively ignored. SciTE '-import c: os web_work' SciTEDoc.html A few commands are currently available although this will expand in the future. SciTE '-open:C: Program Files SciTE SciTEDoc.html' -goto:123 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. 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. For Windows: 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' 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 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. 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. Buffers 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.
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. Sessions 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'. 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'. If 'buffers' variable is set to '0' session management is turned off. 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. 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. 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.
For other encodings set the code.page and character.set properties. Defined variables in properties files Some properties are only available on Windows, GTK+, macOS, or Windows & macOS. Position.left position.top position.width position.height position.maximize 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. Position.tile 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. Buffers 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. 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. Buffers.zorder.switching 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. Are.you.sure are.you.sure.for.build 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.
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. Save.all.for.build SciTE normally saves the current buffer when performing a Compile, Build, or Go command.
To save all buffers set save.all.for.build=1 view.whitespace view.indentation.whitespace Setting view.whitespace to 1 makes SciTE start up with whitespace visible. Setting view.indentation.whitespace to 0 hides visible whitespace inside indentation. Setting view.indentation.whitespace to 1 makes indentation whitespace visible Setting view.indentation.whitespace to 2 makes indentation whitespace only visible whitespace.fore whitespace.back Sets the colours used for displaying all visible whitespace, overriding any styling applied by the lexer.
View.indentation.guides view.indentation.examine view.indentation.examine. Filepattern highlight.indentation.guides Setting view.indentation.guides to 1 displays dotted vertical lines within indentation white space every indent.size columns. 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).
Setting highlight.indentation.guides to 1 highlights the indentation guide associated with a brace when that brace is highlighted. View.eol 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. Eol.mode The default EOL mode (characters that make up line ends) depends on your platform. You can overwrite this behaviour by setting the property to.
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. 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.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 decenders to overflow into the adjacent lines. This mode is incompatible with buffered.draw so will be treated as phases.draw=1 when bufferd.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.
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 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).
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.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. Selection.fore selection.back selection.alpha 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. The translucency of the selection is set with selection.alpha with an alpha of 256 turning translucency off. Caret.fore Sets the colour used for the caret.
Selection.additional.fore selection.additional.back selection.additional.alpha Similar to selection.fore, selection.back, selection.alpha. Sets the colours used for displaying additional selections when multiple selections are enabled or a rectangular selection is made. Caret.additional.blinks Set whether all carets blink. 0 means only the main caret blinks.
Default is 1. Selection.always.visible Set to 1 to show the selection coloured even when SciTE is not the active application.
Default is 0. Caret.line.back caret.line.back.alpha Sets the background colour and translucency used for line containing the caret. Translucency ranges from 0 for completely transparent to 255 for opaque with 256 being opaque and not using translucent drawing code which may be slower. 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.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. 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. If strict is set, the policy is enforced.
The caret is centred on the display if slop is not set, and cannot go in the UZ if slop is set. 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. '3UZ' notation is used to indicate three time the size of the UZ as a distance to the margin. If even is not set, instead of having symmetrical UZs, the left and bottom UZs are extended up to right and top UZs respectively.
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. See the table below to see how these settings interact. Default: xslop, yslop, xeven, yeven=1, width=50, all others = 0. Visible.policy.strict visible.policy.slop visible.policy.lines 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.*. Edge.mode edge.column edge.colour 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. Control.char.symbol Sets the character to use to indicate control characters. If not set, control characters are shown as mnemonics. Error.marker.fore error.marker.back 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. Error.inline style.error.0 style.error.1 style.error.2 style.error.3 To see error messages interspersed with the source code, set error.inline=1. 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. Bookmark.fore bookmark.back bookmark.alpha 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. Find.mark.indicator If set, then the Mark All command in the Find dialog will draw indicators over each string found. This is a with multiple attributes similar to. Find.mark.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80 find.mark 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) Overridden by find.mark.indicator.
Indicators.alpha 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.
Will be overridden by specific indicator definitions such as find.mark.indicator. Indicators.under If set, the indicators are drawn under text or over (by default, it is over).
Will be overridden by specific indicator definitions such as find.mark.indicator. Error.select.line 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. Filepattern 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+. An openpath setting may look like. Abbreviations.*.c=$(SciteUserHome)/c_abbrev.properties api. Filepattern 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.
User.context.menu=|| Next File|IDM_NEXTFILE| Prev File|IDM_PREVFILE| magnification output.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 settings.
The 'All Source' item uses a set of file patterns which combines all the 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+. 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.
For example, *source.patterns.ruby=*.rb;*.rbw; adds the file patterns *.rb and *.rbw to the set of source extensions. Name Set a value to be included in the file type pull down menu in the Open dialog when using the default value for. 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.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 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. 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.command 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 and. 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.
Find.files 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. 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. Find.in.dot 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. Find.in.binary 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. Find.in.directory 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.
Find.in.files.close.on.find Set to 0 to prevent the Find in Files dialog from closing when 'Find' pressed. Code.page output.code.page 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. Code page Value Default (single byte character set) 0 UTF-8 65001 Japanese Shift-JIS 932 Simplified Chinese GBK 936 Korean Wansung 949 Traditional Chinese Big5 950 Korean Johab 1361 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.
This property can not set a single byte character set. If output.code.page is set then it is used for the output pane which otherwise matches the edit pane. Character.set 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.
Character set Value Default 0 Japanese 128 Chinese GB2312 134 Chinese BIG5 136 Korean 129 Greek 161 Eastern European 238 Baltic 186 Turkish 162 Hebrew 177 Arabic 178 Thai 222 Vietnamese 163 Cyrillic (CP866 on GTK+) 866 Cyrillic (CP1251 on Windows, KOI8-R on GTK+) 204 Cyrillic (CP1251 on GTK+) 1251 European with Euro (ISO 8859-15) 1000 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. Ime.interaction 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.
Ime.autocomplete 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. Accessibility 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.
Imports.include imports.exclude These settings control which files are imported by import statements. 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.
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. Import sys if 'Language:Korean' in open (sys.argv [ 1 ]).read (): print ( 'code.page=949' ) print ( 'character.set=129' ) comment.block. Lexer 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. 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. 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 or as a Lua LPeg lexer using.
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.
Filepattern Specifies the path to an external lexer module that will be loaded into Scintilla. Filepattern keywords2. 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. 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++. 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). Stylenumber style. 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', or 'l' for mixed, upper or lower 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.*.
Any style options set in the global style will be inherited by each lexer style unless overridden. 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. 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++. Command.go.*.c=$(FileName) command.go.needs.*.c=g++ $(FileNameExt) -o $(FileName) command.name.
Filepattern command. Filepattern command.is.filter. Filepattern command.subsystem. Filepattern command.save.before. Filepattern command.input.
Filepattern command.replace.selection. Filepattern command.quiet. Filepattern command.mode. Filepattern command.shortcut. 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.
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, command.input.0.*.cc=$(CurrentSelection) would pipe the current selection to the command processes. The command.input property is only supported for subsystem 0 (command line programs).
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 when the command completes. A final command property that is currently supported only on windows 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.
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. 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 Currently, all of these except groupundo are based on individual properties with similar names, and so are not described separately here. The groupundo setting works with subsystem 3 (lua / director), and indicates that SciTE should treat any changes made by the command as a single undo action. A command that uses the groupundo setting should not change which buffer is active in the editor. 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. 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. 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. User.context.menu=Indent|1100| 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. Filepattern command.help.subsystem.
Filepattern 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. Command.scite.help command.scite.help.subsystem Defines a command to be executed for help on the SciTE program itself which normally means displaying this file in a browser.
Time.commands When a command is completed, print the time it took in seconds. Print.magnification 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. Print.colour.mode 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. Print.margins 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. Print.header.format print.footer.format 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. A header setting may look like. Print.header.format=$(FileNameExt) - Printed on $(CurrentDate),$(CurrentTime) - Page $(CurrentPage) print.header.style print.footer.style 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. Export.keep.ext 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). Export.html.wysiwyg export.html.tabs export.html.folding export.html.styleused export.html.title.fullpath 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. 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. Export.rtf.wysiwyg export.rtf.tabs export.rtf.font.face export.rtf.font.size export.rtf.tabsize 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. 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. Export.pdf.magnification export.pdf.font export.pdf.pagesize export.pdf.margins 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.
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. Export.pdf.pagesize is used to set the document's page size, using points (1/72th of an inch) as the unit. Letter paper (8.5 inch x 11 inch) is specified using the values 612,792. Export.pdf.margins sets the widths of the page margins.
Margins defaults to 72 points, or 1 inch. 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.
Export.tex.title.fullpath 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. Export.xml.collapse.spaces export.xml.collapse.lines 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.
Fold Folding is turned on by setting fold=1. Fold.symbols 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. Fold.fore fold.back Sets the colours used for folds. Fold.fore sets the outline colour, fold.back sets the fill. Fold.margin.width Sets the width of the fold margin.
Fold.margin.colour fold.margin.highlight.colour 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 fold.margin.colour=#FF0000 and fold.margin.highlight.colour=#0000FF, the fold margin is a mixture of red and blue. Fold.on.open To automatically fold files as much as possible when loaded, set fold.on.open to 1. Fold.flags 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. Fold.compact 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. Fold.highlight 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).
Fold.highlight.colour Define the colour of highlight. The colour by default is red (#FF0000).
Title.full.path 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'.
Title.show.buffers When set to 1 shows the current buffer number in the title bar. Tabsize tab.size. Filepattern indent.size indent.size. Filepattern use.tabs use.tabs.
Filepattern indent.auto tab.indents backspace.unindents 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. The global tabsize, indent.size, and use.tabs properties can be overridden for files that match a pattern by using the file pattern forms. Indent.size.*.pas=3 If indent.auto is set then indent.size and use.tabs are set according to the contents of the opened document.
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. 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. Indent.automatic indent.opening indent.closing indent.maintain. Filepattern 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. Warning.wrongfile=0,C: Windows Media SFX Glass.wav 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. Fileselector.width fileselector.height 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. Fileselector.show.hidden On macOS setting this to 0 makes the file selector dialog invoked by the Open command not show hidden files.
Locale.properties Set the name of the localisation file. For a multi-user installation this allows each user to set a preferred user interface language. 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.
Locale.properties=$(SciteUserHome)/translations/locale.de.properties translation.missing 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. Menu.language 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: H&ypertext|html|F12| Menu items may be commented out by prefixing the name with '#'. The default value for this setting is built up by combining all settings.
Name Set a value to be included in the Language menu when using the default value for. For example, *language.ruby=Ruby|rb|F9| 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. Menukey.* 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. Menukey.file.exit=Q 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'. 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. Source.default.extensions 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. An example is:.cxx|.cpp|.c|.hxx|.hpp|.h|.bat|.txt|.lua Attempting to open win32 SciTEWin would open win32 SciTEWin.cxx since it matches before win32 SciTEWin.h 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. Ext.lua.startup.script ext.lua.auto.reload ext.lua.reset extension. Filepattern The ext.lua properties are specific to the. The extension. Filepattern property is part of the generic but is currently only used by the Lua Scripting Extension.
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.
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.
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. 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. Aside from ext.lua.startup.script, the extension.
Filepattern 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. 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. Caret.sticky 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.
Properties.directory.enable 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.
Save.path.suggestion 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. Highlight.current.word.indicator=style:roundbox,colour:#0080FF,under,outlinealpha:140,fillalpha:80 The structure uses commas between attributes and a colon between an attribute name and value: attribute value default style one of plain, squiggle, tt, diagonal, strike, hidden, box, roundbox, straightbox, fullbox, dash, dots, squigglelow, dotbox, squigglepixmap, compositionthick, compositionthin, textfore, point, or pointcharacter. Plain colour or color a hex colour value preceded by '#' such as #008020. Black fillalpha the translucency from 0 for completely transparent to 255 for opaque of the fill for roundbox, straightbox and dotbox.
30 outlinealpha the translucency from 0 for completely transparent to 255 for opaque of the outline for roundbox, straightbox and dotbox. 50 under the indicator is drawn under the text. No notunder the indicator is drawn over the text.
Yes Samples: Supporting a new language 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.
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 Scintilla, or put into an external module and loaded when SciTE runs (See lexerpath). 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. Creating API files The.api files can be generated by hand or by using a program. There are also For C/C++ headers, an API file can be generated using and then the (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 utility may be used on these files. To generate an API file for Python modules, there is a. To generate an API file for Java classes, there is a program. Open Selected Filename 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. SciTE in other languages SciTE can be and has been. Building SciTE The procedure for building and installing SciTE is described in the README file in the scite directory. Extending SciTE There are two formal extension interfaces for SciTE, the is for extending SciTE with code compiled into the SciTE executable and the is for manipulating SciTE on Windows from another application.
DON’T let one missed appointment or task put at RISK the entire project! How to SAVE TIME & ELIMINATE ERRORS when Scheduling and Rescheduling related Appointments & Tasks in Outlook. See the Big Picture and have a better perspective of Outlook Project Management (View ALL related Appointments and Tasks for a Project in one screen inside Outlook using the new Project Centre) Take your Outlook Scheduling and Project Management onto a new level.
Create an entire series of related appointments and tasks using templates with no errors! Implement and improve processes for standard projects by creating your own templates that reflects the way your organization works.
Easily and Accurately View, Recalculate and Reschedule ALL affected appointments and tasks when a deadline changes. Do all this INSIDE Outlook Smart Schedules installs a few buttons inside Outlook so you can continue to work the same way you always have. Resulting appointments and tasks synchronize to mobile devices through other Outlook scheduling devices (Iphones, IPads, BlackBerries, Android Phones etc). Add on for Microsoft® Outlook ® which makes it easy to create Appointments and Tasks for you. To start using Smart Schedules, open your Outlook. You will find the following toolbar: (In Outlook 2010) (In Outlook 2007 and below) Smart Schedules Project Centre Click on the 'Project Centre' button to access the Smart Schedules Project Centre: From this centralized Project Centre, you can: • Create and maintain Templates to speed up creation of your project schedules • Use the easy-to-use Wizard to create Appointments and Tasks using the pre-defined Templates.
• Generate scheduled Appointments and Tasks reports. • Email or Export the reports to Microsoft Excel and Microsoft Word formats. Create/Edit Templates From Project Centre, click on 'Create/Edit Templates' link to open the following screen: This screen displays the list of all the schedule templates that you have. Click ‘ Add Templates’ button to create a new schedule template. To add/modify events into a template Note: Events are series of appointments and tasks that are necessary to be done in order to successfully complete the project. From the Create/Edit Templates screen above: • Select the Template that you wish to modify • Click on ' Add Event' link under the events section to open the following screen: Define your event details on the above screen and click Save to add the Event.
You can also use the ‘Edit Event’ or ‘Delete Event’ links to alter the sequence of steps for a template as seen fit. Note: You can add as many event to a template as you want. Using Template to create Appointments and Tasks From the Project Centre, click on 'Create Appts/Tasks' link.
The following 3-step wizard will open: Choose the template that you want to use and follow the easy-to-use Wizard to schedule your appointments and tasks. Reschedule your project appointments and tasks Smart Schedules allows you to reschedule the already created Appointments and Tasks for the selected project.
From the Project Centre, • Select the project that you wish to reschedule from the drop-down. • click on the 'Reschedule' link to open the following Wizard: Note: Any event that has already occurred in the past will be un-ticked and will be displayed in red by default. You can select the specific events that you want to reschedule and click Next to define how you want to shift the appointments and tasks. On the last step of the wizard, you will be presented with the list of events with their respective current schedule times and the new reschedule times that you have defined. Click Finish to apply the new schedule times to the appointments and tasks. Export/Email Reports From the Project Centre, click on 'Reports' link to open the following screen: Choose the options as to how you wish to export/email the reports and click OK. How to Download and Install Smart Schedules for Outlook Download Smart Schedules by clicking on the appropriate button.
Supports Outlook 2003, 2007, 2010. Save the Installation file You will be asked to save the file to disk. Choose Save Fileand the file will be saved to your desktop (or to the folder you set for downloads in your browser options). Run the Downloaded File When the download is done, double-click on the downloaded file. Click on Run to open the Smart Schedules Setup application to guide you through the rest of the installation. Start using Smart Schedules in Microsoft Outlook. Open Outlook to start using Smart Schedules.
In Smart Schedules, you can define the templates once and then use them to quickly schedule all required Tasks and Appointments to get a project completed at the click of a button. Automatically Deploy to Client Computers in Enterprise or Organization If you want to deploy our Outlook addins to your whole enterprise or organization (using Active Directory), please contact us at sales@unitedaddins.com. We will send you a link to an MSI installation package with instructions for customizing and deployment using Windows Server Group Policies. Smart Schedules' price per license is $97.00 USD. Need software licenses for Multiple Users?
Save money with our volume license options. Multi-User Value Pack Discount Per Copy Total Buy 5-User Pack Save 10% $97.00 $87.30 $485 $436.50 Save $48.50 Buy 10-User Pack Save 15% $97.00 $82.45 $970 $824.50 Save $145.50 Buy 25-User Pack Save 20% $97.00 $77.60 $2,425.00 $1,940.00 Save $485.00 Buy 50-User Pack Save 25% $97.00 $72.75 $4,850.00 $3,637.50 Save $1,212.50 Buy 100-User Pack Save 30% $97.00 $67.90 $9,700.00 $6,790.00 Save $2,910.00 Contact us at sales@unitedaddins.com for higher quantities or site and global licensing.