Debugging with SciTE 2 – Additional Tips & Tricks
In this second Debugging with SciTE video I show a few more tips & tricks that I didn’t mention /wasn’t aware of at the time of the first video. This video compliments the last so be sure you watch the first one before this one.
Make sure you play till the end as I demonstrate the AutoHotkey dmp function which allows for easily seeing what text is in an array / object as well as demonstrate how you can use the Output panel as the command shell.
Configuring SciTE language Property files
One of the main reasons I love SciTE is because of the ability to use the ~70 language property files which show Intellisense. I’ve put around 70 of them in this zip file and I’ve listed out the names of them at the bottom of this post.
Configure SciTE language Property files is easy. In your User.Properties file just add something like this
The Properties folder needs to be either in the same directory as where SciTE is installed, or needs to be located in the folder where you have configured your SciTE Home variable to point to.
After importing the properties you want, I also recommend importing them to your language menu as well. This way you can select what language you want to apply to the open file (this can come in pretty handy at times). To do this you’ll still need to be in your User.Properties file. Add something like below. (The & is what will make that letter become an accelerator key)
And here are some notes to help understand what can be done when Configuring SciTE language Property files:
# Define the Lexer menu, Each item contains three parts: menu string | file extension | keyboard equivelant
# The only keys allowed currently are based on F-keys and alphabetic keys and look like # [Ctrl+][Shift+][Fn|a] such as F12 or Ctrl+Shift+D.
# A ‘&’ may be placed before a letter to be used as an accelerator. Each element is terminated by ‘|’. For example: H&ypertext|html|F12|
Here are the language property files provided in my zip file.
SciTE Home variable
SciTE is an awesome editor which I use on multiple computers. Instead of trying to keep track of my User.Properties files on each computer I’ve created a SciTE Home variable under my System settings.
This tells SciTE to use it for my default locations. If you set it up on each computer you use you won’t have to worry about having different configuration settings. While I predominately use it for AutoHotkey, I also show how you can setup importing other property files and configure the settings under languages. Just remember you’ll need a folder that is accessible across each computer (I use DropBox to keep mine synced)
Here’s a video walking through the process of creating a SciTE Home variable.
Out of the box, SciTE is a great editor! I’m willing to bet the majority of people never customize it to their needs. They are missing out! In the below video I demonstrate how I customize the SciTE User.Properties file which allows me to tailor it very specifically to my needs.
In the below video I walk through my User.Properties file which you can download from here. I don’t think anybody should have all of the settings I have, however I wanted to give y’all the syntax in case you want to borrow sections (without having to type it out.) Please be sure you backup your SciTEUser.properties file before doing any of this (I recommend you email yourself a copy to have as a static backup file just in case…)
In the video I mentioned a few important points that you need to review before using my file. By going to
Control Panel –> System–>Advanced System Settings–>Advanced–>Environmental Variables…
I created a system variable entitled: Scite_Home. Having this variable present means I can control where SciTE looks for the User.Properties file. (This was important for me because I work on many computers and wanted to have the same settings on all the computers. I also ran into issues that SciTE4AHK would over-write my SciTE User Properties file when I updated it.)
Video review of my SciTE User.Properties file
I hope you take the time to play with your configuration. It can be frustrating at times however, in the long run, it is definitely worth it!