I don't know, maybe @kugel- has more to add, but I can't imagine I'd go to some open source project and suggest adding the Geany project configuration file - I'd be stoned to death because everyone uses a different editor.

I use Geany also for work and there we happily accept editor-specific files in the repos if it helps our engineers to get their job done. This is especially true for Windows and OSX stuff where we commit the whole VS and Xcode project metadata (multiple files).

I also wouldn't take it as a given that each and every FOSS project would stone you to death, that seems extremely exaggerated. I can imagine a lot of project maintainers aren't opposed if it helps on-boarding contributors or making their lifes any easier. After all, it's just a text file that doesn't hurt anybody else.

If we accept geany.geany within Geany itself it would indicate that the scheme is working as intended, so I wouldn't say no.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.