From ArchWiki
Revision as of 01:49, 27 February 2012 by Speed (talk | contribs) (Starting maintenance of this page. More to come.)
Jump to: navigation, search

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:SciTE#)

SciTE is a Scintilla based text editor. Originally built to demonstrate Scintilla, it has grown to be a generally useful editor with facilities for building and running programs. It is best used for jobs with simple configurations.


Install scite, available in the Official Repositories.


This is a short introduction, might help at start:

Start with some general settings, please note that I just add these settings to the files in /usr/share/scite, most of the stuff can also be set in files in your ~. Refer to scite docs for filenames on that. general settings which are mostly scattered over the file. Find the lines and tweak them. Code:

# I like my Scite with tabs and a statusbar, displaying line and column

#comment out this line or set it to 0 to have the message pane displayed
#under the editor's textfield not besides

#display line numbers (create enough space for 4 digits)

# ask b4 automatically reload an altered file on disk
# show  name and number of my tab in titlebar
# save the buffer state in a file and reload on startup

# allows 25 tabs

# I plain hate indents with tabulators and using 8 spaces is waste of place
# converts tabulator hits to spaces

# some sane fontsettings: - the ! activates pango -> AA fonts
# sets them all to similar sizes and monospace font
# after the if PLAT_GTK these must be tabublators in intendation like in a Makefile!
	font.base=font:!bitstream vera sans mono,size:9
	font.small=font:!bitstream vera sans mono,size:8
	font.comment=font:!bitstream vera sans mono,italics,size:9$(font.comment)
	font.text=font:!bitstream vera sans mono,size:9
	font.text.comment=font:!bitstream vera sans mono,size:8
	font.embedded.base=font:!bitstream vera sans mono,size:9
	font.embedded.comment=font:!bitstream vera sans mono,size:9
	font.monospace=font:!bitstream vera sans mono,size:9
	font.vbs=font:!bitstream vera sans mono,italics,size:9

# uuh, netscape - long time not seen, replace with firefox
	command.print.*=a2ps "$(FileNameExt)""file:///$(SciteDefaultHome)/SciTEDoc.html"

# add a vertical line at column 80

go on to file; to get the advantages you need the php.api and the from HERE. You also find api files for ASP.

#replace netscape with mozilla-firefox again
	command.go.$(file.patterns.web)=mozilla-firefox "file:///$(FilePath)"
# load the .api file which I downloaded from the web; it contains, per line,
# a short explanation of each command
# $file.patterns.php is defined for *.php and friends by file extensions
# the calltips for the hypertext lexer shall not be case sensitive
# define how the calltipps should be parsed, the following is the same as
# the standard anyway, but might be overwritten by some people in SciTEGlobal
# some calltips have an additionally explanation after the final ")"
#   -this makes display them in a second line
# autocopleter stuff
# defines which type of characters let the autocompletion pop up
# also the autocompletion should not be case sensitive since, grrr php and html

There can be defined 10 commands file.pattern, these are some for html and one for php files. Actually Scite is capable of parsing the output of commands for line and column like it does for the php -l command further down or the already defined perl checker. Unfortunately it doesn't work for tidy, it always open a blank new tab on clicking instead of placing the cursor at the correct position :/

Show error messages of tidy, doesn't change the file

# extend the "Extras" menu with some commands
# Tidy Checking$(file.patterns.web)=HTML Tidy Validate
command.1.$(file.patterns.web)=tidy -quiet -errors $(FilePath)

Use Tidy to format(indent and wrap at line 80) and clean your code. This command is defined this way: - save file to disk - have tidy parsing it and rewrite the output directly back to the file - re-read in the file and show in editor -> consequence: !!! THERE IS NO UNDO ON THIS COMMAND !!! Since we set 'activate' a warning will popup, if we really wanna reload it. So you can decide based on the output in message pane.

# Tidy Cleanup and indent$(file.patterns.web)=HTML Tidy Cleanup
command.2.$(file.patterns.web)=tidy -i -wrap 80 -m $(FilePath)$(file.patterns.web)=1$(file.patterns.web)=1

This activates the php linter which finds parsing errors like missing line ends or braces. A click on the error message highlights the error in editor and places the cursor there.

# activate a lint checker for php files$(file.patterns.php)=Check PHP syntax
command.1.$(file.patterns.php)=php -l $(FilePath)

To open files in a new tab of the current instance, rather than a new instance (window)

# Checking