Piotr Fusik: > 1. Initial line checking should be done if no style is found using the > filename > rather than just when there's no extension.
OK. > For me, XML and HTML are much > more important than #!. I'd limit this to files that start with exactly "<?xml" (ignoring Unicode BOM). > 2. It should not be limited to "#!" and full-word matching. I think that > any sequence of characters should be matched anywhere in the first line > (for example, "/perl" => perl), or a regexp (/^#!\s*\S*perl(\s|$)/ -> > perl). Matching shouldn't be too easy as many files include other language names in header comments. Regular expressions get too complex and the listed one isn't compatible with SciTE. Robert Roessler: > How about a global prop like "enable.auto.language" with "no", "if no > match on extension", and "always (allow override of extension)" > values... backed by an ordered set of RE-matching rules which could be > replaced and/or reordered and/or supplemented in User prop files? So this is only going to be permitted in user.properties so there can be no confusion over priority? What I liked about the original idea was that the language names can be added to that language's .properties file with little chance of interference. Neil _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
