#NO OPTION TO RUN SCRIPT IN SCITE EDITOR CODE#

The following example is fairly strange, but shows how one can bind a shortcut followed by a letter to an operation. One could use it to keep track of any declarations typed, etc. One key difference is that it never interferes with normal character processing. OnEditorLine is a similar event, except it happens when the user enters a line in the editor pane. If ok then if res then print( 'result= '.res) end else print(res) ')' end local f,err = loadstring(line, 'local') Local sub = string.sub if sub(line,1,2) = prompt then Here is a simple but effective Lua console for SciTE: OnOutputLine only fires when a line is typed into the output pane. Local was_whitespace = string.find(w.ch, '%s') The OnWord handler receives a table, which has fields word, startp, endp, ch which are respectively the word found, its initial position, the final position, and the character found immediately after the word. Here is the 'lazy' word substitution example rewritten for extman. They are built on the basic events, and are included for convenience. In addition to the standard SciTE Lua events, extman provides OnWord, OnEditorLine and OnOutputLine. In a similar fashion, there is scite_OnChar, scite_OnSave, etc - except for OnUserListSelection, which is handled differently. It is now perfectly possible for another script to listen to the OnOpen event, without causing conflict. For instance, scite_OnOpen will add a function to the list of handlers called by the OnOpen event. (The latest version of extman also provides OnOpenSwitch, which is called when a file is made active, either by opening or by switching buffers. Scite_Command 'Switch Buffer|do_buffer_list|Ctrl+J' function do_buffer_list() Using extman, this script looks like this (the function buffer_switch is the same) Such a script would interfere with any other script that had a need to watch these events. Consider SciteBufferSwitch the handlers OnOpen, OnSwitchFile and OnUserListSelection are all overriden to keep track of buffer changes and present a drop-down list of buffers. The SciTE Lua interface is very powerful, but presently there is no way to make non-trivial scripts 'play nice' with each other.

#NO OPTION TO RUN SCRIPT IN SCITE EDITOR CODE#

You can find extman at Files:wiki_insecure/editors/SciTE/a the examples and code are in Files:wiki_insecure/editors/SciTE/extman.zip it is entirely written in Lua and works with any recent SciTE release. There are some extra examples included:* a, which provides a simple interactive Lua prompt.* select_a, which allows you to select the whole of a string (or a comment) with a double-click* select_a, which allows you to select blocks by a margin click next to a fold line. It also allows you to reload Lua scripts controlled by extman with 'Reload Script' (Ctrl+Shift+R). This latest version () corrects a serious bug in the Linux version, and uses a more robust scheme to determine whether an entered line is in the editor or output pane. Lua-users wiki: Scite Ext Man Scite Ext Man

No option to run script in scite editor