[Github-comments] [geany/geany] YAML cannot be overridden (#2205)

[JanAxelsson]

Regarding order in determining filetype and pattern :

 I looked at the linked PR, and found this one : 2166 (https://github.com/geany/geany/pull/2166 <https://github.com/geany/geany/pull/2166>).  That seems to be a solution to the problem I had.



Regarding plug-in system for adding filetypes :


I do not ask you to swap in/out hard coded compiled C++ and C parsers.

 I think the use case which I and many others have, is to add a filetype through adding a filetypes.xxx.conf file in the user directory.  These are not touching the compiled C++ and C parsers, but they use them.

My thought, which I sensed from the replies were not understood, is that new filetypes do not conflict with the build in syntax highlighters at all.  Reason being, that me and many others have created new filetypes that can be manually installed into the user folder, but requires you to realize that they are actually available at the Geany Wiki.

I believe that some mechanism to introduce a new language filetype would be feasible, since the installation procedure would be exactly the same as for manual downloading, putting things in the correct folder and editing filetype_extensions.conf.

My thought was that an easy way to select new languages (filetypes) would benefit Geany with more users.

Thank you for your time and help, and if there is something I can do myself more than adding the docker-compose and editing the Dockerfile filetypes to the Geany Wiki I would gladly help.  Problem is that it seems too daunting to learn how to do this.

Thanks again.  If you wish you can close this issue.  Do you want me to make another issue suggesting this plug-in of new filetypes ?

/Jan





> 24 juni 2019 kl. 12:12 skrev elextr <notifications at github.com>:
> 
> oops, hit comment too soon :)
> 
> 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.
> 
> Somebody just needs to make one or more PRs.
> 
> 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
> 
> At the moment the syntax highlighting lexers and the symbol parsers are C++ and C code (respectively) compiled into Geany, so those can't be added at runtime.
> 
> It would be possible to make them be loaded as plugins, but its a big job, and will need a lot of hard coded configuration to be changed to be modifyable from the plugin or a configuration file. And somebody has to contribute it.
> 
> —
> 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=AG7S4VR7YIBIU5PWDQE5MJDP4CMXRA5CNFSM4H2Z2CFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYMOL6Y#issuecomment-504948219>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG7S4VXASBWNU2AHDLSVEFDP4CMXRANCNFSM4H2Z2CFA>.
> 



-- 
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-505035652
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20190624/25241bdc/attachment-0001.html>