> new names would be nice, but whilst we keep exposing Geany internals we 
> should leave the names the same otherwise we have to change all uses to the 
> new name.

You misunderstood me, I meant better names for these **new** functions, before 
they're published into the API for the first time, so we don't need to 
rename/alias them later or break any plugins that start using them.

-- 
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/pull/2234#issuecomment-518439333

Reply via email to