bug#70532: sort: Mention counting fields from the end

2024-04-26 Thread Dan Jacobson
> "PB" == Pádraig Brady writes: PB> All good suggestions. I'll at least add an example along the lines of: PB> awk '{print $NF, $0}' | sort -k1,1 | cut -f2- -d' ' OK, also say what it's doing. Not everybody knows awk. Also join(1) needs a tip added. Users might want to join on e.g., the s

bug#70601: join(1) info page -o: too hazy at first

2024-04-26 Thread Dan Jacobson
The join main page is really clear, -o FORMAT obey FORMAT while constructing output line A base hit on the first pitch. The info page on the other hand, ‘-o FIELD-LIST’ ‘-o auto’ If the keyword ‘auto’ is specified, infer the output format from the first line in eac

bug#70600: trailing whitespace spotted in join info pages

2024-04-26 Thread Dan Jacobson
The join info pages have tons of trailing whitespace. sed s/$/$/ reveals: ‘sort -u file1 file2’Union of unsorted files$ $ ‘sort file1 file2 | uniq -d’ Intersection of unsorted files$ $ ‘sort file1 fil

bug#70599: join vs. numeric order

2024-04-26 Thread Dan Jacobson
(info "(coreutils) Sorting files for join") needs to talk about numeric order. $ seq 111|join --check-order - /dev/null join: -:10: is not sorted: 10 So the info manual needs to mention 'Even though your files might be in perfect "sort --numeric-sort" order, you need to make them into plain "sort

bug#70586: cp walks dir differently than rm and is hitting "File name too long" where this could be avoided

2024-04-26 Thread Arkadiusz Miśkiewicz via GNU coreutils Bug Reports
Hello. rm -r while deleting a directory that's longer than PATH_MAX walks it in a way to avoid hitting max limit $ (for i in `seq 1 2000`; do mkdir 1234567890123456789012345678901234567890; cd 1234567890123456789012345678901234567890; done) $ rm -r 1234567890123456789012345678901234567890