@ell1e what is "common"? This is hard to define in a general way and the JSON standard does *not* allow comments.
@d5l6 I wonder if it wouldn't be better to keep the custom filetype and just add the Scintilla JSON lexer to Geany and update the custom filetype definition to use it. Otherwise we need also a migration path for existing users or they will end up with two JSON filetypes. Not sure which one would be used then. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/2454#issuecomment-629520411
