Hello,

I'm new to Geany, and I really like the core application. I agree that it hits the sweet spot between features and simplicity (as the website intro suggests), however I'm surprised that out-of-the-box how hardly it's suitable for front-end development. I put quite some time to configure Geany for better front-end development support and also created a new repo for it: geany-config-front-end-development (improving an old one), but it's still far from perfect.

I've some concrete questions to someone who knows Geany as a product better than I do:

Geany supports adding Global tags files, and suggests to use the Tagmanager format. Using Geany, from what source should users generate global tags files for the cleanest possible results, and least manual work e.g. for generic autocompletions support for CSS3 and JavaScript ES6, or libraries like jQuery?
Geany is a mature product, but without shipping these configuration files (filedefs for popular files like LESS and SCSS, and tags and snippets for CSS, HTML and JS), it might feel very incomplete for many. What's behind the decision not shipping these files by default (which to me – maybe naively – seems like a small contribution to a complex application, but one that would hugely improve its usability)?

I'm asking these primarily from curiosity, and to find out the best possible way of contribution if I keep improving the repository above.

Thanks in advance,
Márton Lente

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