bug#43684: Problem with numerical splitting with files > 90*l
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 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 > > That reminds me it was also discussed at: > http://www.pixelbeat.org/docs/coreutils-gotchas.html#split >
bug#43684: Problem with numerical splitting with files > 90*l
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: https://lists.gnu.org/archive/html/bug-coreutils/2017-02/msg00050.html http://bugs.gnu.org/25832 That reminds me it was also discussed at: http://www.pixelbeat.org/docs/coreutils-gotchas.html#split
bug#43707: [PATCH] stat: use a colon before a list, and don't use backticks as quotes
On 29/09/2020 13:31, Benno Schulenberg wrote: * src/stat.c (usage): Replace a mistaken semicolon with a colon, and replace mistaken backticks with single quotes. Also reorder some words, for clarity. Pushed at: https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v8.32-55-gebaffa509 thanks! Pádraig
bug#43684: Problem with numerical splitting with files > 90*l
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 regards, - assaf
bug#43707: [PATCH] stat: use a colon before a list, and don't use backticks as quotes
* src/stat.c (usage): Replace a mistaken semicolon with a colon, and replace mistaken backticks with single quotes. Also reorder some words, for clarity. --- src/stat.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/stat.c b/src/stat.c index 4e6c2aa86..1c09073a2 100644 --- a/src/stat.c +++ b/src/stat.c @@ -1717,10 +1717,10 @@ Display file or file system status.\n\ fputs (VERSION_OPTION_DESCRIPTION, stdout); fputs (_("\n\ -The --cached MODE argument can be; always, never, or default.\n\ -`always` will use cached attributes if available, while\n\ -`never` will try to synchronize with the latest attributes, and\n\ -`default` will leave it up to the underlying file system.\n\ +The MODE argument of --cached can be: always, never, or default.\n\ +'always' will use cached attributes if available, while\n\ +'never' will try to synchronize with the latest attributes, and\n\ +'default' will leave it up to the underlying file system.\n\ "), stdout); fputs (_("\n\ -- 2.25.4
bug#43684: Problem with numerical splitting with files > 90*l
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 (so that `cat lat_lon_* > lat_lon_full` works as expected) with --suffix-length=2 the numbering works correctly, and quits after 99. Well if there is more data than can be accommodated in 100 files it will error like: $ truncate -s 101 file $ split -b1 -d --suffix-length=2 file split: output file suffixes exhausted You can specify a larger --suffix-length to have both more natural looking numbers, and correct globbing order. thanks, Pádraig