Le 27/01/2016 14:32, Alain Aupeix a écrit : Does it mean you don't see the new language in the "File type" list in the UI, or that it's not automatically applied to your .prg files? If the new file tyep doesn't appear at all, it probably means the file is in the wrong place/has wrong permissions. If it's not detected automatically, it might be because names are case sensitive. if your filetype is named "filetypes.harbour.conf", your entry in filetype_extensions.conf need to mention "harbour" exactly. If you get the proper filetype yet no syntax highlighting or anything, it's probably that you failed to set the lexer_filetype under stettings in your custom filetype. Custom filetypes have additional keys you need to fill in. (BTW, you probably also want to fill in tag_parser). Regards, Colomban

Le 27/01/2016 15:24, Alain Aupeix a écrit : Parsing symbols from the file, which populates the Symbols pane, and yes, is also used for auto-completion purposes (and type highlighting). Well, extracting symbols is done by some C code, so if none of the existing parsers work for your case, you'll have to write it -- a CTags parser -- and integrate it. Harder, but not impossible. However, if C was (mostly) good, just use tag_parser=C and done. You can also try C++, C#, Java, Vala or whatnot, depending on who much alike your language is similar to one of those ("similar" here having a subtle meaning of "how well the parser for it handles your language"). Regards, Colomban