On 12/7/18 4:13 PM, patrick keshishian wrote:
> On Fri, Dec 07, 2018 at 08:41:21AM +0100, Martijn van Duren wrote:
>> I ran into a few minor nuisances with sed's -i mode, which are mostly
>> compatible with gnu sed, but I reckon we should address.
>>
>> The problem is sed works by writing the
On Fri, Dec 07, 2018 at 08:41:21AM +0100, Martijn van Duren wrote:
> I ran into a few minor nuisances with sed's -i mode, which are mostly
> compatible with gnu sed, but I reckon we should address.
>
> The problem is sed works by writing the output to a second file in the
> same directory as the
I ran into a few minor nuisances with sed's -i mode, which are mostly
compatible with gnu sed, but I reckon we should address.
The problem is sed works by writing the output to a second file in the
same directory as the original and after completion renaming the file
to the original. This has
