GIMP has Script Fu (and a newer Python interface) which has been used for wonderfully time-saving things (e.g. process a thousand images with the same plugins and settings and such, implement your own custom processing tools by combining existing ones, etc.)
I'm sure the same sorts of things can be done with Krita, though I'm not familiar with it.
As for LibreOffice, that seems obvious. An easy/automated way to get data into and out of it for processing in other programs. An automated way to process lots of documents that need to stay in LibreOffice but need the same change performed on them (currency conversion, date format normalization, copyright update, etc.).
It's the same reason you'd want anything to be programmable: Automating away the tedious stuff.
> GIMP has Script Fu (and a newer Python interface) which has been used for wonderfully time-saving things (e.g. process a thousand images with the same plugins and settings and such, implement your own custom processing tools by combining existing ones, etc.)
Begin scriptable and having a CLI are two orthogonal concepts. With Script FU, GIMP itself executes scripts. If gimp had a CLI it means that you could be able to do stuff like "gimp --select-pen 2px solid black --moveTo 0 0 --lineTo 100 100 --lineTo 50 50" for instance (for which I don't see the point of using GIMP to do).
Now you are picking on minor wording choices. You asked for clarification and when it was provided you start beating up the person who responded with meaningful content.
I'm sure the same sorts of things can be done with Krita, though I'm not familiar with it.
As for LibreOffice, that seems obvious. An easy/automated way to get data into and out of it for processing in other programs. An automated way to process lots of documents that need to stay in LibreOffice but need the same change performed on them (currency conversion, date format normalization, copyright update, etc.).
It's the same reason you'd want anything to be programmable: Automating away the tedious stuff.