Hello,

@elextr I see your points, but from a UX perspective I totally disagree. Just let me clarify what I meant:

I think additional language support makes a text editor better in most cases. 'Proper' CSS, HTML JavaScript etc. support wouldn't make Geany less suitable for C or C++ development, but the lack of it stops most front-end developers from using it.
I put 'best' in a quotation mark in my previous response to not suggest there is anything like best. What I meant is that researching and trying existing, but scattered config helper files throughout the internet, or creating new ones is something that most new users won't do, but look elsewhere. For example: there're currently three CSS Tags files in the wiki – a new user would rather trust the package maintainers to bundle the 'most complete' one instead of researching for him/herself this 'low-level' compontent first.

There may be nothing wrong with all these. The solution might be a good-enough PR in future that brings these features to Geany – I meant this under 'shipping', which I see as an ambitious, helpful contribution. Until then, I hope that repos like the one I made myself and many others will be a good helper for users who also like this great editor, and would use it for web development.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.