bin/safe-sed should default to writing the new file
The GDK probably knows better than I do, how to configure everything. Custom configuration is just a pain to maintain and the benefits seem to be for a very small set of users.
This makes me conclude that safe-sed is a very verbose annoyance which should just write the new config file and don't waste any more of my time.
The feature was originally introduced in !628 (merged)
Edited by Toon Claes