|
|
SciTE |
On Windows GDI, font names have been encoded in UTF-8 since Scintilla 3.5.3. This matches the Direct2D code path. Perviously they were encoded in the local code page. Giving the name in UTF-8 or Ascii may solve the problem.
This is most likely a problem with DirectDraw on your graphics card. Different methods of drawing can be tried by modifying the technology setting.
Use these properties:
The use.monospaced property was removed as people were using it to ask for fixed width fonts and then requiring support to cope with its limitations. The correct way to set fixed width fonts is here.
line.numbers has been replaced with two properties: line.margin.visible and line.margin.width which are explained earlier in the main SciTE document.
You need to change the style settings. The main change is in the user options file to the global default style and caret colour but you may have to change other style settings to make this work well:
The output pane often lists error and warning messages and is styled by the "errorlist" lexer. The default errorlist styles are found in others.properties. To change the output pane background to black and the default text to white set
To avoid slow performance the horizontal scroll bar does not automatically adjust. You can use the horizontal.scroll.width property to change the horizontal scroll range.
Multiple buffers must be allocated by setting, for example, buffers=10 in your SciTEGlobal.properties. To have the tab bar visible upon starting SciTE, set tabbar.visible=1. You can also set tabbar.hide.one=0 to always show tabs, or 1 to hide when only one file is open. tabbar.multiline=1 splits tabs across various lines if necessary.
Goto Options | Open Global Options File and uncomment
Make sure that the path to your compiler is set correctly on your system. Try to execute from console the same command you get in SciTE and see if it works. You can also search in your [language].properties for the compile commands used. If you have a different compiler or use different arguments, edit the commands to suit your needs. The lines to look for:
In your properties file, you'll need to add some lines:
command.name.number.filepattern
(e.g.: command.name.1.$(file.patterns.web)=HTML Tidy)
This defines the Text that will appear on the Tools Menu.
command.number.filepattern
(e.g.: command.1.$(file.patterns.web)=tidy -i -wrap 0 -m $(FilePath) )
This is the actual command that SciTE executes. You should provide the appropriate paths, options and parameters as you would from a command line. See SciTEDoc.html for more information on parameters and how to make SciTE prompt a Parameters Dialog.
command.is.filter.number.filepattern
(e.g.: command.is.filter.1.$(file.patterns.web)=1)
The external application may have modified your file, so setting this to true makes SciTE reload the
file after execution of the command if load.on.activate=1.
command.subsystem.number.filepattern
(e.g.: command.subsystem.1.$(file.patterns.web)=2)
This is for Windows and defines the subsystem through which the program is called. See SciTEDoc.html for more information on this.
You can set a command for all files using * as a file pattern. Up to 10 commands (0 - 9) can be defined in the Tools Menu at any time. Commands also get executed with Ctrl+number.
This is similar to adding to the tools menu except that you set the name to be empty. Then the command is included in user.shortcuts by adding 1100 to produce its command ID. For example,
It is possible to replace a string in all opened buffers with the Replace in Buffers button in the Replace dialog. However this button is hidden by default, it can be displayed with find.replace.advanced=1.
Line wrapping slows SciTE down and this can be turned off with wrap=0.
No.
The "Transform backslash expressions" option allows using \n and \r but that option does not work with regular expressions.
The set of error message formats is embedded in the Scintilla and SciTE code. To add support for another compiler, you will need to add a new style to scintilla/include/Scintilla.iface after the other SCE_ERR_* values, run HFacer.py, edit RecogniseErrorListLine in scintilla/src/LexOthers.cxx to recognise the error message, and edit DecodeMessage in scite/src/SciTEBuffers.cxx to extract the file name and line number.
Linux distributions now often set the locale to UTF-8 by, for example, setting LANG=en_US.UTF-8. gcc takes this as an indication that it can use any Unicode character encoded as UTF-8 so quotes using ‘these’ rather than ASCII. To see these as intended, set
On some versions of Windows, associating a particular file type with SciTE does not allow paths containing spaces to work. To fix this, the path variable %1 needs to be surrounded by double quotes. This is done either directly in the registry or through the Explorer in Tools | Folder Options | File Types | (Select type) | Advanced | open | Edit. Change the "Application used to perform action" field to be similar to
For C++ and similar languages, explicit folds can be added with //{ and //} . This feature can be turned off with