[Geany-Devel] Proposal from the Mint distro

[Matthew Brush]

On 12-10-21 01:13 PM, Colomban Wendling wrote:
> Le 21/10/2012 21:52, Matthew Brush a écrit :
>> [...]
>>
>> But that doesn't mean we couldn't extend which widgets can be hidden via
>> the config file by adding more keys to it. I like this way the best
>> because I can also use it for the (future) Mac bundle (it already has a
>> customized geany.conf in the bundle to change some defaults).
>
> (OT, but should really a Geany MacOS port hide some stuff???  Changing
> the default keybindings to be more MacOS-ish may indeed be sensible, but
> changing Geany?)
>

(There's more stuff, like using the correct fonts, commands, etc. Also, 
Apple thinks its users are idiots and so most programs seem to come with 
very simplified defaults, and lacking a decent text editor, a simplified 
Geany would be very useful for general text editing, further, it's 
nearly impossible to do development on OSX without having XCode and so 
having another "full featured" IDE is less useful. That being said, I 
don't want a "different Geany", just to change the defaults so that you 
have to explicitly enable "advanced" features/widgets to make it more 
"Mac-like" by default.)

>> The other options of Mint maintaining a fork to simplify Geany
>> themselves or doing it by means of distro package tricks means any
>> "improvements" couldn't easily be re-used for the Mac bundle (or other
>> DEs using it as a default text editor) and they would have to be
>> "unforked" or duplicated.
>
> I'm sorry if I sound harsh, but why are you (all) saying that, why
> couldn't such a "fork" be use by somebody else??  It's not like putting
> Mint-specific code, is it?
>
> I'm not saying forking is the way to go (I'm less and less sure what
> should be done BTW), but I mean, if one just create a geany-light/-lite
>   project and push that to a publicly-available repository (anywhere,
> even on linuxmint.com) anybody could clone it and use it, or even
> package it.  It's not a "nah!  it's mine!  don't touch it!"-thing, is it?
>

I said "couldn't *easily* be re-used". Of course you can still use the 
downstream changes but it's more work compared to having them all in the 
same place.

Either way, it's all pointless to discuss until someone writes down the 
changes that are needed and we see whether they belong in Geany or not 
instead of just theorizing.

Cheers,
Matthew Brush