A couple of Scite-EZ questions

First off. I have Visual Studio on my computer. Recently Newgate Ludd mentioned;

"If you have access to Visual Studio then Scite-Ez has the advantage of allowing use of the preprocessor which is a godsend"

I already run lslint after scripting to check errors. How do I go about preprocessing with Visual Studio??????

Next. After scripting, all of my indents look nice and neat in Scite-EZ but when I paste into SL or into the forum here they look like c**p, with some parts indented waaaaaay over. Any ideas what I might possibly have set wrong in Scite-EZ? I am currently using tabsize = 4 and indent size = 4. CR & LF are selected as Line End Characters.

Jesse,

Scite-Ez has rules for esl, extended lsl that uses the visual studio preprocessor to allow you to #define, #include etc.

check out the lsl properties file for more info.

Thank you for getting back to me Newgie!!!

I was in the lsl.properties file when I read you reply

# ESL files use the C preprocessor (Hugh Perkins)
# set to 0 to strip comments (smaller LSL output, useful if your'e hitting the 64kb limit)
NO_STRIP_COMMENT=1

if NO_STRIP_COMMENT
esl.strip.comment=/C
#command.compile.*.esl=cmd /c cl /nologo /X /u $(esl.strip.comment) /Tc"$(FileNameExt)" /EP >"$(FileNameExt).tmp" && "$(SciteDefaultHome)\SciTE.exe" "-open(FileNameExt).tmp"
#command.compile.*.esl=cmd /c cl /nologo /X /u $(esl.strip.comment) /Tc"$(FileNameExt)" /EP >"$(FileName).lsl"
# preprocess ESL script, strip whitespace and write LSL file
command.compile.*.esl=cmd /c cl /nologo /X /u $(esl.strip.comment) /Tc"$(FileNameExt)" /EP >"$(FileName).wsl" && "$(SciteDefaultHome)\stripper.exe" "$(FileName).wsl" "$(FileName).lsl" && del "$(FileName).wsl"
command.compile.*.lsl="C:\lsl\lslint.exe" "$(FileNameExt)"

# put LSL or ESL script into clipboard
command.go.$(file.patterns.lsl)="$(SciteDefaultHome)\clipboard.exe" "$(FileName).lsl"
#command.go.needs.*.esl=cmd /c cl /nologo /X /u $(esl.strip.comment) /Tc"$(FileNameExt)" /EP >"$(FileName).lsl"
# ESL scripts are "compiled" first, then the resulting LSL file is put into clipboard (by the line above)
command.go.needs.*.esl=$(command.compile.*.esl)
#cmd /c cl /nologo /X /u $(esl.strip.comment) /Tc"$(FileNameExt)" /EP >"$(FileName).wsl" && "$(SciteDefaultHome)\stripper.exe" "$(FileName).wsl" "$(FileName).lsl" && del "$(FileName).wsl" && "$(SciteDefaultHome)\clipboard.exe" "$(FileName).lsl"

That is the way it is set right now. Anything I should somment out or uncomment? I just compiled an esl file and came up with this error:
"'cl' is not recognized as an internal or external command,
operable program or batch file."
So I am guessing that 'cl' probably stands for command line maybe. SHould I be pointing it at "C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\".

Sorry for being a pain but I am always looking to add to my knowledge base some.

OK hang on there. I found a thread showing the changes needed in the lsl.properties file. Now it is throwing a an error stating that the application has failed to start because mspdb80.dll was not found. Let me muck around some more.

Gooooooo Jesse.....

Sounds like one of the Microsoft DLL's. What version of VS?
I've several different versions installed on various machines

Professional full version. I was cheating and just pasted the address without giving it full thought. I actually needed to point it at the cl.exe file in the bin folder and move a copy of the dll there too. Still not working thou but I am getting there.

Ah finally success. I had started with Qarl's Qlab scripts. Finally realised that I had to rename them all from .lsl to .esl for Scite-EZ to process them into .lsl files. eeeeek I feel like I have been through a root canal!.

But anyways, now I have learned something new for the day.

If you dont learn something new everyday you are probably dead.
- anon