bug#71307: Mention recommended styles

(info "(coreutils) sort invocation") First problem. We see e.g., "try the ‘--debug’ option" but '--debug' is not clickable. If we want to go to its section to read more, the best we can do is isearch-forward for it. Next problem. We read Also note that the ‘n’ modifier was applied to the fi

bug#71171: ls -U, -f: document the other half of the story too

Man ls says: -U do not sort; list entries in directory order Please make it say: -U do not sort; list entries in the order they were given on the command line, and files within directories using their directories' order And on (info "(coreutils) Sorting the outp

bug#70876: Making join Info examples easier to test

Today I tried to run these examples on (info "(coreutils) Paired and unpaired lines") it says: All examples below use the following two (pre-sorted) input files: $ cat file1 $ cat file2 a 1 a A b 2

bug#70874: Don't use two column Info examples, e.g. for join

I would say please give up attempting two column examples, e.g., on (info "(coreutils) Paired and unpaired lines") Yes, they look great in the standalone Info reader, $ info But in emacs -Q -f info we start to see problems. And then e.g., using https://www.jidanni.org/comp/configuration/.emacs th

bug#70873: join --return-error-if-any-unmatched-lines

join should have an option to return an error value in the shell's $? if any lines are not matched. Currently the man page doesn't even mention a return value. So it is not set in stone yet. Currently one must save -v output in a file then use test -s do detect if there were any non-matched lines

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

> "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

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

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

(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#70532: sort: Mention counting fields from the end

In (info "(coreutils) sort invocation") be sure to add an example of a way or workaround for counting fields from the end of the line. E.g., we want to sort on the last field, but don't know for sure how many fields a line might contain. E.g., sort by surname, when lines consist of First [Middle...

bug#67619: stty on Chromebook

Seen on Chromebook: $ stty speed 38400 $ stty speed 1200 38400 $ stty speed 1200 1200 coreutils 9.4

bug#67543: mv -i e/a f/a g: asks bad

Here the program should think ahead, so that it won't ask a question that it could already know the answer to. $ mkdir e f g $ touch e/a f/a $ mv -i e/a f/a g mv: overwrite 'g/a'? y mv: will not overwrite just-created 'g/a' with 'f/a' I'm not sure what it should do. Just don't have it ask things t

bug#62492: Note each util's URL on their Info pages too, not just man page

Just the other day I wanted to tell my friends about e.g., the uniq command. I wanted to "share" it with them. OK on (info "(coreutils) uniq invocation") there is no "share" URL. However on $ man uniq there is!: Full documentation or av

bug#62249: uniq -D long option name missing from man page

man uniq has all the other long option names, except for -D's -d, --repeated only print duplicate lines, one for each group -D print all duplicate lines --all-repeated[=METHOD] like -D, but allow separating groups with an empty line;

bug#61696: Warn about sort --numeric-sort --unique data loss

At (info "(coreutils) sort invocation") it says For example, ‘sort -n -u’ inspects only the value of the initial numeric string when checking for uniqueness, whereas ‘sort -n | uniq’ inspects the entire line. *Note uniq invocation::. OK, but you still need to add a warning about data loss.

bug#61467: Don't assume short/long options for error messages

$ sort --human-numeric-sort -nr sort: options '-hn' are incompatible Say instead: sort: options --human-numeric-sort (-h), and --numeric-sort (-n), are incompatible. Else some projects might be delayed by days, as some people need to email other people to ask... "Can't blame me. That's not what

bug#61248: uniq --unique needs examples

BV> While an example is always nice, isn't the last part of the above BV> exactly telling what it's doing? That is for experts to know. The rest of us need examples, sort of like your idea, (please modify): $ echo a a a b c c b b d b | xargs --max-args=1 | uniq --unique b d b

bug#61248: uniq --unique needs examples

uniq INFO page says: ‘-u’ ‘--unique’ Discard the last line that would be output for a repeated input group. When used by itself, this option causes ‘uniq’ to print unique lines, and nothing else. This really needs some examples, to help people understand what it means.

bug#52453: Full timezone name

>>>>> "PE" == Paul Eggert writes: PE> On 12/12/21 07:27, 積丹尼 Dan Jacobson wrote: >> Also mention something about how to get the full timezone name. PE> Unfortunately at the coreutils level that information is not available PE> in any portable or reliable w

bug#52453: Full timezone name

On (info "(coreutils) Time conversion specifiers") ‘%Z’ alphabetic time zone abbreviation (e.g., ‘EDT’), or nothing if no time zone is determinable. See ‘%z’ for how it is determined. Also mention something about how to get the full timezone name. E.g., show instead of CST: Central St

bug#51288: Break date SYNOPSIS into two sections

On the 'date' man and info pages, SYNOPSIS date [OPTION]... [+FORMAT] date [-u|--utc|--universal] [MMDDhhmm[[CC]YY][.ss]] Synopses: date [OPTION]... [+FORMAT] date [-u|--utc|--universal] [ MMDDhhmm[[CC]YY][.ss] ] please break these down into: printing the date: da

bug#50694: ls and cpio's idea of "six months ago" are slightly different

What a headache. "Six months ago" means slightly different things to cpio and ls. And ls documents do say exactly what, and cpio documents don't even say six months. $ cat prover set -eu cd /tmp for i in `seq 170 190` do touch -d "$i days ago" x { env - ls -l x|tr -s ' ' ls

bug#49764: tr invocation INFO page missing list of options

(info "(coreutils) tr invocation") all the options don't appear together on the same page. Only the man page's DESCRIPTION has them all together.

bug#49503: Mention workarounds, so one could achieve the Debian version sorting algorithm

(info "(coreutils) Differences from the official Debian Algorithm") and (info "(coreutils) Minus/Hyphen and Colon characters") could mention workarounds, so one could indeed achieve the Debian Algorithm. Or mention the only way is to use dpkg --compare-versions (on pairs only.)

bug#48248: tr docs: mention what to expect now vs. future

(info "(coreutils) tr invocation") says Currently ‘tr’ fully supports only single-byte characters. Eventually it will support multibyte characters; when it does, the ‘-C’ And the man page has no warning at all. #BUG. Please add one. BTW, $ echo 哇|tr 哇 123 123 It works fine! (People will t

bug#47891: sort --numeric-sort-Extra-Strength

Let's face it, sort, no matter what --option, or LC_... value, just can't achieve this order: 3－1號邊 3號之1 3號之2 30 What's the miracle kid (me) doing right that sort(1) just can't sort out yet? Mom told me "Just sort by numbers." See https://www.jidanni.org/geo/house_numbering/sorting/ in your spa

bug#47859: Additional seq outlandish example: seq 0 dangers

On (info "(coreutils) seq invocation") we read Be careful when using ‘seq’ with outlandish values: otherwise you may... Here's another 'fun/sad/DDOS yourself' example you might add: One day I wrote a Makefile, m: seq 0 9|sed s/$$/號.html/|xargs make but before using it, I though I'll

bug#47858: Document that FULLWIDTH DIGITs boggle coreutils brain currently

(info "(coreutils) Correct/Incorrect ordering and Expected/Unexpected results") needs to "admit" or "at least mention" that "coreutils just hasn't thought about FULLWIDTH DIGITs yet." I.e., Europeans are in luck. East Asians are out of luck. $ seq 9 11|sort 10 11 9 $ seq 9 11|sort -n 9 10 11 $ se

bug#47700: Backup options vs. file extensions

(info "(coreutils) Backup options") is great, except, it needs examples of how one can preserve file extension with it. E.g., x.jpg~ messes up plenty of viewers, but x~.jpg is fine. Same with numbered backups. So the page should discuss this problem, and mention workarounds.

bug#47703: Mention if ln -s needs -r, or ln -r needs -s

man ln says: -r, --relative create symbolic links relative to link location -s, --symbolic make symbolic links instead of hard links Does -s need -r, or -r need -s? Hard to tell from the man page. Had to find out the 'hard' way. Please mention the a

bug#47702: wc man page: first you are talking about bytes, then you are talking about characters

Man wc says Print newline, word, and byte counts for each FILE, and a total line if more than one FILE is specified. A word is a non-zero-length sequence of characters delimited by white space. first you are talking about bytes, then you are talking about characters. So fo

bug#47701: Add ln --dry-run

$ ln -rbsv ~/Downloads/*/95*[0-9].jpg xiangpianjibentu 'xiangpianjibentu/95212025.jpg' -> '../../../../Downloads/ViewLarge_Draw_files/95212025.jpg' 'xiangpianjibentu/95212033.jpg' -> '../../../../Downloads/ViecccwLarge_Draw_files/95212033.jpg' 'xiangpianjibentu/95212025.jpg~' ~ 'xiangpianjibe

bug#47353: Numbered backups also need kept-new-versions else will grow out of control

All I am saying is 'to acknowledge the hazards'... 'Advisory on prolonged use'. 'Note about health effects of unattended use.' For all the user knows reading (info "(coreutils) Backup options") maybe numbered backups even just means one backup, numbered ...1.

bug#47353: Numbered backups also need kept-new-versions else will grow out of control

> "CE" == Chris Elvidge writes: CE> So 'use common sense to limit disk space used' has to be stated in the CE> manual? Hmmm, yes. And also mention in the manual that e.g., emacs has methods to trim these automatically, but coreutils hasn't implemented them yet. Else users will write elabora

bug#47353: Numbered backups also need kept-new-versions else will grow out of control

Or (info "(coreutils) Backup options") should "admit" that "Numbered backups need to be trimmed occasionally by the user, lest the fill up the disk."

bug#47352: Numbered backups also need kept-new-versions else will grow out of control

(info "(coreutils) Backup options") has "numbered", but without a corresponding limit factor, these can grow beyond belief. So coreutils also needs a way to say like emacs does: kept-new-versions is a variable defined in ‘files.el’. Documentation: Number of newest versions to keep when a new numb

bug#46346: wc --human-readable or --verbose

wc needs a --verbose option. Else one is forced to do: $ file=e.html; echo $file:; for i in bytes chars lines words; do echo -en $i:\\t; wc --$i < $file; done e.html: bytes: 31655 chars: 29141 lines: 643 words: 1275 I mean sometimes we want to send the output to a real person, and currently

bug#46060: Offer ls --limit=...

> "PE" == Paul Eggert writes: PE> That argument would apply to any program, no? "cat", "diff", "sh", PE> "node", PE> Not sure why "ls" needs a convenience flag that would complicate the PE> documentation and maintenance and be so rarely useful. OK, then I'll close the bug then.

bug#46060: Offer ls --limit=...

E.g., "What is API pagination? Some APIs, such as Contacts can return millions of results. We obviously can't return all of them at once, so we need to return a subset - or a page - at a time. This technique is called paging and is common to most APIs. Paging can be implemented in many different wa

bug#46060: Offer ls --limit=...

Sure, it is against the https://en.wikipedia.org/wiki/Unix_philosophy, but just like SQL has LIMIT, and $ unicode --help -m MAXCOUNT, --max=MAXCOUNT Maximal number of codepoints to display... Just like "we want to stop pollution at the source", not always "clean up after

bug#46060: Offer ls --limit=...

I hereby propose "ls --limit=..." $ ls --limit=1 # Would only print one result item: A You might say: "Jacobson, just use "ls|sed q". Closed: Worksforme." Ah, but I am talking about items, not lines: $ ls A B C D E F G H I J K L $ ls -C|sed 2q A B C D E F G H $ ls -C --limit=2 A

bug#44975: Warn that fold will wreck UTF-8

On (info "(coreutils) fold invocation") warn that fold will wreck UTF-8 files, shattering any multibyte character that unfortunately lies near its chopper. (GNU coreutils) 8.32

bug#44959: date error message should say -I

Well OK, but when and when not to use the "=" is not revealed by the otherwise detailed error messages. So unless the user checks the manual, they will never "get it".

bug#44960: date --expose-flags

date +%Y-%m-%dT%H:%M:%S%z ^I meant %:z > Then one needn't use trial and error (Driving my point home.)

bug#44960: date --expose-flags

I got this brilliant idea. Let's say one likes the output of $ date --iso-8601=seconds 2020-11-30T21:15:47+08:00 but wants to know "how you did it?" Hmmm, no assistance from $ date --iso-8601=seconds --debug 2020-11-30T21:15:50+08:00 Ah, if only there were a: $ date --iso-8601=seconds --expose-

bug#44959: date error message should say -I

$ date -I=seconds date: invalid argument ‘=seconds’ for ‘--iso-8601’ Hey, that is a valid argument for --iso-8601. (But not for -I, so say that instead.) Here is a real invalid argument: $ date --iso-8601=secondsz date: invalid argument ‘secondsz’ for ‘--iso-8601’ date (GNU coreutils) 8.32

bug#44770: chown: warn about the dot when encountering it

Maybe print warning messages when encountering the dot, (info "(coreutils) chown invocation") Else Grandpa won't ever know, https://github.com/scop/bash-completion/issues/468 until one day when it's too late... (And his program starts messing things up on some other system.)

bug#40943: nl: add way to exclude matching lines from getting numbered!

(info "(coreutils) nl invocation") says ‘pBRE’ number only lines that contain a match for the basic regular expression BRE. *Note Regular Expressions: (grep)Regular Expressions. OK, but add a new functionality: ‘PBRE’ Do NOT number lines that cont

bug#40942: Clean up mailing list confusion on web page

https://www.gnu.org/software/coreutils/ mentions coreut...@gnu.org and bug-coreutils@gnu.org (and the term mailing list and the term bug tracker many times, all intertwined and perhaps repeating.) Maybe only mention each one once, with a description of what they are below it. So that would be a t

bug#40633: Document / implement sorting via absolute value

(info "(coreutils) sort invocation") should mention how to sort via absolute value, or add an option to do it. Currently one must use e.g., $ seq -2 2|perl -pe 's/^(-)(.*)/$2$1/;' | sort -n 0 1 1- 2 2-

bug#40363: date: add Julian day number output format

date(1) should add "Julian day number" or the "Astronomical day number" (see (info "(emacs) Calendar Systems") output format. Else for crontab(5) one must do # Run once per 48 hours (every other day), even across week, month, and year boundaries: 33 22 * * * expr $(date +\%s) /

bug#39613: stat(1) shouldn't call permissions "Access..."

(info "(coreutils) stat invocation") says, • %a - Access rights in octal (note ‘#’ and ‘0’ printf flags) • %A - Access rights in human readable form But man find says, -perm mode File's permission bits are exactly mode (octal or symbolic). Since an exact match is requi

bug#39017: Mention more about uniq failure exit status

(info "(coreutils) uniq invocation") says An exit status of zero indicates success, and a nonzero value indicates failure. The user wonders: "Failure to make a file unique because it was already unique?" Be more explicit.

bug#38780: date: next feb 11

date -d should add a way to say "next feb 11" or "next 2/11" etc. E.g., at(1) knows we are always talking about the coming Feb. 11, and not the one that has already passed in the current year. Just like we can say "next Friday" and "last Friday" currently.

bug#36220: ls -l: maddening mixed left right justifications with numeric ids

> "PE" == Paul Eggert writes: PE> On 6/17/19 8:12 AM, Pádraig Brady wrote: PE> I prefer the current ("maddening") behavior, as it gives the reader a PE> useful signal that the user is numeric rather than textual. This is PE> particularly important when a user name consists entirely of digits,

bug#36220: ls -l: maddening mixed left right justifications with numeric ids

> "PB" == Pádraig Brady writes: PB> to know if it was a common issue, as I've not encountered it at least. Well as the anbox Android emulator could possibly become very popular, ls should be ready for a big influx of numeric ids.

bug#36220: ls -l: maddening mixed left right justifications with numeric ids

Some files might only have numeric user ids, # ls -l -rw-r--r-- 1 777 root 0 06-15 10:14 a -rw-r--r-- 1 root 77 0 06-15 10:11 b -rw-r--r-- 1 root root 0 06-15 10:12 c -rw-r--r-- 1 root777 0 06-15 10:12 d Well it turns out an undocumented feature is that numeric ids are justified in t

bug#35748: Add cut FIELD-LIST examples

> "EB" == Eric Blake writes: EB> No need to open a second bug to tell us that the first was not a problem EB> after all. I'm merging the two bugs in the database, and marking the EB> issue closed. It takes several minutes before the bug number is created, so there is a tradeoff between proper

bug#35748: Add cut FIELD-LIST examples

Oh, I see, it is mentioned above it. Sure wish "(see above)" was there.

bug#35747: Add cut FIELD-LIST examples

On (info "(coreutils) cut invocation") with no examples for ‘-f FIELD-LIST’ ‘--fields=FIELD-LIST’ Select for printing only the fields listed in FIELD-LIST. Fields are separated by a TAB character by default. Also print any line that contains no delimiter character,

bug#35343: sort: printing characters: define

Well all I know is e.g., perl's man perlrecharclass is more detailed than (info "(coreutils) Character sets") section, (which (info "(coreutils) sort invocation") perhaps should also link to.) Anyways, coreutils should at least link to a definite statement...

bug#35431: Mention "cp -l a b is exactly equivalent to ln a b"

On (info "(coreutils) cp invocation") at ‘-l’ ‘--link’ Make hard links instead of copies of non-directories. Mention "Exactly equivalent to ln." or "cp -l a b is exactly equivalent to ln a b." Or if not, mention why.

bug#35343: sort: printing characters: define

(info "(coreutils) sort invocation") says ‘-i’ ‘--ignore-nonprinting’ Ignore nonprinting characters. The ‘LC_CTYPE’ locale determines character types... Well this leaves the user high and dry trying to figure out what you mean by printing characters. Is SPC a printing character he won

bug#35336: date should respect TIME_STYLE too

All the other utilities respect the environment variable ‘TIME_STYLE’, except date(1) itself! Date should be no different...

bug#35335: touch --verbose

Say, rm, cp, mv have --verbose. How about for touch too? Then one wouldn't need $ set -x; touch /tmp/{a,b,c}.el; set +x + touch /tmp/a.el /tmp/b.el /tmp/c.el to see what it was touching or not.

bug#34988: mv: check before asking users useless questions

> "LSS" == Leslie S Satenstein writes: LSS> Did you consider that more than one terminal can be open, and at the LSS> second terminal, "b" could be renamed before replying to the mv LSS> command? I don't know about all that. Let's hope the designers consider all aspects.

bug#34988: mv: check before asking users useless questions

$ mv a b mv: overwrite 'b'? y mv: cannot overwrite non-directory 'b' with directory 'a' User thinks well why didn't you check before uselessly asking me? Full story: $ mkdir a $ touch b mv: overwrite 'b'? y mv: cannot overwrite non-directory 'b' with directory 'a' $ \mv a b mv: cannot overwrite n

bug#34664: Mention wc default action on man page

Well > Print newline, word, and byte counts might sound like > Play movies, audio files, and even ... Sort of like a list of capabilities. > "PB" == Pádraig Brady writes: PB> I'm confused. It says 'bytes', and means it. PB> One has to specify -m to select characters. But OK, fine.

bug#34670: Implement "seq infinity"

I can do $ sleep infinity so why not $ seq infinity also?

bug#34669: Document sleep infinity

$ man sleep | grep -ic infinity 0 $ sleep --help | grep -ic infinity 0 $ info sleep | grep -ic infinity 0 $ /bin/sleep infinity #But it still works, so please document it.

bug#34664: Mention wc default action on man page

INFO says By default, ‘wc’ prints three counts: the newline, words, and byte and wc --help even more so. Alas man wc doesn't say if what we are looking at is bytes or characters, so kindly mention the default on the man page!

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

Thanks for working on this guys, hopefully users will one day no longer be faced with (yes, seemingly) random errors. $ ls -l | sed 2!d drwxr-xr-x 14 jidanni jidanni 4096 2016-12-24 AndroidMisc $ ls -l | sed 2q total 157780 drwxr-xr-x 14 jidanni jidanni 4096 2016-12-24 AndroidMisc ls: w

bug#34490: console the user that his -n in sort --debug -n was seen

> "PB" == Pádraig Brady writes: PB> Fair point. I'm thinking of this extra qualification: PB> sort: text ordering performed using ‘en_IE.UTF-8’ sorting rules Maybe say 'LC_CTYPE=en_IE.UTF-8' sorting rules PB> sort: text ordering performed usi

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

(I recall I heard about 50 years ago when pipe buffers first came to Unix they were supposed to be invisible to the user...)

bug#34475: Mention even more worries for test -a

By the way https://lists.gnu.org/archive/html/bug-bash/2019-02/msg00052.html says "... contradictory description in the coreutils info document."

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

> "EB" == Eric Blake writes: >> And no fair saying "just save the output" (could be big) "into a file >> first, and do head(1) or sed(1) on that." EB> If you have an app that exits noisily on write failures to an early-exit EB> pipe, your solutions are to quit ignoring SIGPIPE, or to change

bug#34490: console the user that his -n in sort --debug -n was seen

Can you please have assure the user in that message it makes that it has indeed seen his -n/--numeric-sort. $ sort --debug sort: using simple byte comparison $ sort --debug --numeric-sort sort: using simple byte comparison unchanged. User gets nervous. sort (GNU coreutils)

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

> "AG" == Assaf Gordon writes: AG> The errors are not "random" - they happen because you explicitly AG> cut short the output of a program. Well the user thinks "hey I cut short 5 lines, 45 lines, 495 lines, and then one I got a job at a big company and cut short 4995 lines and got this error

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

Things start out cheery, but quickly get ugly, $ for i in 9 99 999 9; do seq $i|sort -n|sed 5q|wc -l; done 5 5 5 5 sort: write failed: 'standard output': Broken pipe sort: write error 5 sort: write failed: 'standard output': Broken pipe sort: write error Therefore, kindly add a sort --li

bug#34475: Mention even more worries for test -a

First, on the test(1) man page, at EXPRESSION1 -a EXPRESSION2 both EXPRESSION1 and EXPRESSION2 are true EXPRESSION1 -o EXPRESSION2 either EXPRESSION1 or EXPRESSION2 is true Say instead EXPRESSION1 -a EXPRESSION2 both EXPRESSION1 a

bug#34347: At least add 2nd comm error message after output

(info "(coreutils) comm invocation") "Before ‘comm’ can be used, the input files must be sorted" "If an input file is diagnosed as being unsorted, the ‘comm’ command will exit with a nonzero status (and the output should not be used).

bug#34026: mention that long options aren't always as good as short options

Yes do warn in the manual, as here root (so no $HOME) expected tilde expansion... Thanks.

bug#34026: mention that long options aren't always as good as short options

On (info "(coreutils) Common options") mention that, though clearer, long options aren't always as good as short options, $ touch --reference=~jidanni/.pcmanx /cf/pcmanx_time touch: failed to get attributes of '~jidanni/.pcmanx/pcmanx': No such file or directory Unless one removes the '=': $ touc

bug#34009: warn that mkdir --mode doesn't affect parents created

On man mkdir -m, --mode=MODE set file mode (as in chmod), not a=rwx - umask -p, --parents no error if existing, make parent directories as needed do warn that --mode doesn't affect any parents created. $ mkdir --mode 700 -p /tmp/g/h/i $ find /tmp/g -ls

bug#26902: good invalid dates vs. bad invalid dates

Maybe it should try to pass on to the user at least an error code: Invalid date: error code 0754, or even better, an mention of what error it hit.

bug#33025: Add examples of why one would want to "sort" something "randomly"

> "AG" == Assaf Gordon writes: AG> (It doesn't deal with "why", that is left to the users to decide when AG> they need it, but it shows clear examples of how to use it). Maybe add "For example, you might want to hear your songs in a fresh fun order. Or make sure your program still works even

bug#33577: ls lacks null terminator option

Fine. Put a message on top of (info "(coreutils) ls invocation") saying that your pipes are better.

bug#33577: ls lacks null terminator option

Are you saying you want to enhance find(1) to sort its output?

bug#33577: ls lacks null terminator option

Don't let that ls colors stuff fool you. It originally didn't have that.

bug#33577: ls lacks null terminator option

(Probably The Unix Programming Environment by K & P.)

bug#33577: ls lacks null terminator option

Bob, I remember from my K&R Unix book that ls can be used in scripts. In fact that is why $ ls acts different than $ ls | cat Plus there are lots of things ls can do that find cannot. For instance sorting. How are you going to do $ ls -t with find?

bug#33577: ls lacks null terminator option

For files with blanks in their names, one shouldn't need this workaround: $ ls -t | tr \\n \\0 | xargs -0 more > /tmp/z.txt Please add a --print0 option. like find(1) has. ls (GNU coreutils) 8.30

bug#23302: mention what are nonprinting characters

Good! You need to then tie all the documentation you found, into the coreutils documentation, as the official declaration of what you mean. Just like "man perlrecharclass - Perl Regular Expression Character Classes" does. I mean one cannot just hope the user will "Google" and then land on "Wikipedi

bug#23302: mention what are nonprinting characters

Yes but every program has slightly different sets of non-printing characters, so they need to list them exactly.

bug#21349: acknowledged by developer (Re: bug#21349: who shows no users nowadays on Debian)

(Today on Debian I see $ who jidanni pts/02018-10-25 06:26 (:0) So maybe this is fixed.)

bug#18479: acknowledged by developer ()

As you can see, the Subject got damaged somehow when sending this message to me. (Subject: Re: bug#18479 acknowledged by developer ()) > "GbTS" == GNU bug Tracking System writes: GbTS> This is an automatic notification regarding your bug report GbTS> #18479: date -d 'today - month', GbTS> wh

bug#14971: acknowledged by developer (Re: bug#14971: split man page table mushed)

Say, can we get the final information just from this email next time, just like in Debian. Where one doesn't need to click on the link to see how the bug was solved. > "GbTS" == GNU bug Tracking System writes: GbTS> This is an automatic notification regarding your bug report GbTS> #14971: sp

bug#18328: can't say date -d '8pm -0500' though other combos work

AG> I hope to get to this bug soon. Good.

bug#33025: Add examples of why one would want to "sort" something "randomly"

On (info "(coreutils) sort invocation") ‘-R’ ‘--random-sort’ ‘--sort=random’ Sort by hashing the input keys and then sorting the hash values. Choose the hash function at random, ensuring that it is free of collisions so that differing keys have differing hash values. This is l

bug#31055: Document ls -Ur -fr

(info "(coreutils) Sorting the output") says ‘-r’ ‘--reverse’ Reverse whatever the sorting method is—e.g., list files in reverse alphabetical order, youngest first, smallest first, or whatever. OK but mention 'whatever' doesn't mean -U, -f, because they are sorted in "unsorted" order. I

  1   2   3   4   >