Mark W. Gabby-Li

Thanks. For full clarity, I believe my Windows installs came from the old "SciTE for Windows" installers, which may have had different versions of the property files? I see the Windows installers are no longer available. I seem to remember they were provided by a third party rather than the project itself? Perhaps there was some mistake when packaging them and they included user-customized property file by accident, or perhaps they had intentional customizations.

Found it! html.properties in C:\ProgramData\SciTE\. The broken property is in a Windows platform block! This is why it was happening for me but not you, you must be on a different platform (I was also not able to replicate it on Linux, so I just booted into Windows and found the error): if PLAT_WIN [...] command.is.filter.1.*=1

Found it! html.properties in C:\ProgramData\SciTE\, I think this is installed by default on Windows. This is why it was happening for me but not you, you must be on a different platform (I was also not able to replicate it on Linux, so I just booted into Windows and found the error): if PLAT_WIN [...] command.is.filter.1.*=1

Found it! html.properties in C:\ProgramData\SciTE\, I think this is installed by default on Windows: ``` if PLAT_WIN command.is.filter.1.*=1 ```

Found it! html.properties in C:\ProgramData\SciTE\, I think this is installed by default on Windows: ``` if PLAT_WIN [...] command.is.filter.1.*=1 ```

Digging into my properties, I don't see any filter settings at all for any commands, nor any use of command.mode. I've attached all the options files and my Lua startup script to this comment. Note that I'm on Windows and I've seen this behavior on the latest in hg as of my report. When the call is made to get the filter status of the command in the JobMode constructor, propName is command.is.filter.1., and fileNameExt is empty.

Sure, but that still means that a command that is set as a filter (not that I know what that means) will produce this spurious error message? Also perhaps the code that job mode is calling is assuming that all files have extensions, which could be what is causing some of the unpredictable behavior? I'd have to dig into that more though, ideally with a debugger. (never mind about the -1 mod time comment, I think I misunderstood.) I will look at my properties later, I don't have them on hand right...

Sure, but that still means that a command that is set as a filter (not that I know what that means) will produce this spurious error message? Also perhaps the code that job mode is calling is assuming that all files have extensions, which could be what is causing some of the unpredictable behavior? I'd have to dig into that more though, ideally with a debugger. And the code is absolutely setting the file mod time to -1, which based on the use of that value seems to mismatch the intent; the code that...