[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: csplit 'no-clobber' option
From: |
Shehu Dikko |
Subject: |
Re: csplit 'no-clobber' option |
Date: |
Wed, 19 Jan 2022 19:41:28 +0100 |
User-agent: |
Mutt/2.1.5 (2021-12-30) |
* Padraig Brady [20220119 17:45:00]:
> On 19/01/2022 10:36, Shehu Dikko wrote:
>> [....]
>> % csplit -n 1 -f "" --suppress-matched -sz ../mbox1 '/^From /' '{*}'
>> % csplit -n 1 -f "" --no-clobber --suppress-matched -sz ../mbox2 '/^From /'
>> '{*}'
>> % ls
>> 0 1 2 3 4 5
>>
>> Kindly consider a 'no-clobber' option.
>
> [...] Also if you were to add such an option, it would be appropriate
> to add to the split(1) command also. If we were to implement this for
> either split(1) or csplit(1), the interface might be
> --existing-file={overwrite,skip,fail}, with overwrite being the
> current default behavior.
Excellent.
> Another option would be to have the user specify a starting number for
> each invocation. We previously discussed adding a --suffix-offset
> option to csplit(1) to support this:
> https://lists.gnu.org/archive/html/coreutils/2020-08/msg00008.html
I am not so keen on this as it would involve the extra step of figuring
out where to start. Stick with the suggested --existing-file options.
regards,
s h e h u