bug#43684: Problem with numerical splitting with files > 90*l

2020-09-29 Thread ned haughton
Fair enough. I didn't see anything about that in the help or man page, perhaps a note should be added there? On Wed., 30 Sep. 2020, 7:11 am Pádraig Brady, wrote: > On 29/09/2020 15:20, Assaf Gordon wrote: > > > >> On 29/09/2020 02:18, ned haughton wrote: > >>> When splitting with -d, the

bug#43684: Problem with numerical splitting with files > 90*l

2020-09-29 Thread Pádraig Brady
On 29/09/2020 15:20, Assaf Gordon wrote: On 29/09/2020 02:18, ned haughton wrote: When splitting with -d, the numbering screws up after 89: In addition to Pádraig explanation, please see previous similar discussion here:

bug#43684: Problem with numerical splitting with files > 90*l

2020-09-29 Thread Assaf Gordon
On 29/09/2020 02:18, ned haughton wrote: When splitting with -d, the numbering screws up after 89: In addition to Pádraig explanation, please see previous similar discussion here: https://lists.gnu.org/archive/html/bug-coreutils/2017-02/msg00050.html http://bugs.gnu.org/25832

bug#43684: Problem with numerical splitting with files > 90*l

2020-09-29 Thread Pádraig Brady
tag 43684 notabug close 43684 stop On 29/09/2020 02:18, ned haughton wrote: When splitting with -d, the numbering screws up after 89: It behaves like that on purpose so that there is no limit on the number of file names to split, and so that normal globbing will result in the correct order

bug#43684: Problem with numerical splitting with files > 90*l

2020-09-28 Thread ned haughton
When splitting with -d, the numbering screws up after 89: ``` $ wc -l ../lat_lon_full 110324 ../lat_lon_full $ split -d ../lat_lon_full lat_lon_ $ ls lat_lon_00  lat_lon_09  lat_lon_18  lat_lon_27  lat_lon_36 lat_lon_45  lat_lon_54  lat_lon_63  lat_lon_72  lat_lon_81 lat_lon_9000