I have done some changes to the fasmw in the way to add plug-in support soon (and by the way I've fixed some bugs), and have also started the separate versioning for the fasmw interface - currently it is 0.90 (while the core is still 1.47). This will also allow to include some kind of "whatsnew" file for the interface changes in future versions.
Also there is small new feature added: now "Optimal fill on saving" option doesn't convert to tabs any "meaning" spaces, like those inside the quoted strings.

Cool.

To Privalov:
Wouldnt it be better to search for include files within a directory(ies) specified in "INCLUDE" env.var ? It'd be much faster & simplier to write
than
P.S. Thanks for such unbelievable project, Privalov !

Another question: Does FASM check each path separated by ";" in the environment variable??

No it's just handled exactly the same as in batch files - if you enclose some word with percent characters, it is replaced with its value from environment. It has nothing common with the standard treatment of path variables in other compilers. I've done it this way because it suits fasm's core philosophy the best - it's quite universal, system-independent and allows you to use any variable names, whatever you wish. You can for example define in fasmw.ini the variable Win32 with the value being full path to the include file you're using the most, and then just do:

each time.