Thanks a lot for the replies. I have updated my dockerfile-dockercompose filetype in the wiki from your suggestion, which worked great. It resolved having to change installed files.
CURRENT ISSUE ============== As I understand, it there are two things that I have missed. I wonder if they can somehow be improved or documented (pardon me if I missed them being documented). - YAML cannot be removed, and is hard coded as a filetype. Is this really necessary? If necessary, it would be great to document what filetypes are hard-coded and locked. Also, the solution to zero it out (’YAML=' in user config) would be great to point out. - The search order for the rules are as pointed out by Colomban a bit random, and it would as Colomban wrote make great sense if the user-setting always overrides the default. Can this be implemented? SUGGESTION ============ This could be submitted as an additional issue, but I add it in this one if you don’t mind, since they are related. One thing which I believe would make it even better is the following : Either add the new filetypes that people have put up on the Wiki to the default installation, or make it easy to add them for a novice. Things like the Dockerfiles are in much greater demand today than some of the other INCLUDED file types, but Geany is probably quickly skipped by people developing for Docker, since Dockerfiles don’t work out of the box. Would it be possible to add a filetype plug-in interface, where missing filetypes are downloaded from some repository or just from an URL. What would be needed for such a function is to place the filetypes.xxx.conf into the user filedefs folder, and to amend the user filetype_extensions.conf. The latter may of course have a minimal change of causing conflicts, but can be resolved manually from the Tools/Configuration files menu Again, thanks for the prompt replies and the great work you are doing. I really love Geany, and it has been my standard editor for decades. /Jan > 24 juni 2019 kl. 02:45(:17.000) skrev elextr <[email protected]>: > > You are correct that YAML is a built-in filetype, and as such can't be > removed, but you can make your YML named filetype and map the file extensions > to that instead of the YAML filetype as @b4n <https://github.com/b4n> > explained. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/geany/geany/issues/2205?email_source=notifications&email_token=AG7S4VU42IY4KXIPF7JHXY3P4AKJ3A5CNFSM4H2Z2CFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLLC3Y#issuecomment-504803695>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AG7S4VX46O46UM2NJLZ7LP3P4AKJ3ANCNFSM4H2Z2CFA>. > -- 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/issues/2205#issuecomment-504921510
