Martin Barrett: > More detail: SciTE versions 1.66 and 1.67 for Windows. "mono.properties" > is a properties file with monospace font assignment and some colors > tweaked. I first tried > > C:\c2c\wscite\scite.exe "-import mono" FILETOEDIT
That is the syntax which could work if the code were tweaked a bit. > C:\c2c\wscite\scite.exe "-import:mono" FILETOEDIT, and No "import:" isn't one of the director commands. > Then I tried putting some conditional logic into SciTEUser, governed by > a switch WT=1, and tried: > > C:\c2c\wscite\scite.exe -WT=1 FILETOEDIT > > This didn't work either. Is it that SciTEGlobal.properties and > SciTEUser.properties are scanned *before any* command-line options are > processed? Yes, that looks to be the case. > The documentation isn't wholly clear about when the > command-line options are processed. And if the properties files are read > again (when a file is (re-)loaded?), are all the properties reset to > default first? SciTE tries to avoid reloading the files unless they are changed. The file's properties are reevaluated when the file is switched to but that doesn't reevaluate if tests which are done at load time. I don't think that you will get your preferred behaviour without modifying SciTE. The code to look at is the ReadLine in SciTEBase::ProcessCommandLine which doesn't handle "import mono" bacuase of the lack of a directory to base the import from. Neil _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
