no OPTIONS header before the options on the cat man page

There is no OPTIONS header before the options on the cat man page. Maybe even other man pages too. ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

touch: often I want to protect myself from myself

The touch info file does talk about permissions, but it seems not to talk about the case when I can reset the modification time despite permissions, $ whoami jidanni $ ls -l a -rw-r--r--1 jidanni jidanni 4370 2004-08-21 03:15 a $ chmod 0 a $ touch a $ ls -l a --1 jidanni jid

cp -upv copies even when not newer

$ man cp -u, --update copy only when the SOURCE file is newer $ echo ooo>c $ cp -upv c e `c' -> `e' $ test c -nt e;echo $? #is it newer? No. 1 $ cp -upv c e `c' -> `e' cp (coreutils) 5.0.91 ___ Bug-coreutils mailing list [EMAIL PRO

test -n STRING and test STRING differ

The docs make it look like test -n STRING and test STRING do the same. However, $ /usr/bin/test ``; echo $? 1 $ /usr/bin/test -n ``; echo $? 0 $ test ``; echo $? 1 $ test -n ``; echo $? 0 ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu

Re: test -n STRING and test STRING differ

Paul> I don't see any bug. Well, you've got to admit that docs like [-n] STRING the length of STRING is nonzero `-n STRING' `STRING' True if the length of STRING is nonzero. and bash's -n STRING STRING True if string is not emp

plain test(1) with no arguments is not documented

Ah ha, plain $ test with no arguments is not documented. The closest thing documented is $ test STRING but when $ string=; test $string then sorry. Not documented. man test, help test, info test, /usr/bin/[ --help, nope, not documented. If the result is not defined, still document that fact. And,

Re: plain test(1) with no arguments is not documented

>> And, document plain >> $ test -n >> which acts differently than plain >> $ test Paul> That's already documented, as "test STRING". -n is the STRING here. The perfect "gotcha". Paul> The details are in the manual: it's too much to put into the usage Paul> string. Perhaps put it here

stat(1): SEE ALSO lsattr(1)

The stat(1) man page should mention to "SEE ALSO lsattr(1) if on Linux", else one might go on http://bugs.debian.org/256760 style goose chases. ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

env: mention variables the shell wouldn't allow one to set

Please mention in the env docs, any qualms one should have about e.g., $ env k-o=4 ... whereas $ k-o=4 or $ export k-o won't work. At least say "one can even set variables the shell wouldn't allow you to set. E.g.," ___ Bug-coreutils mailing list [EMAI

Re: cp -up forever

P> Here's a patch: P> http://lists.gnu.org/archive/html/bug-coreutils/2004-03/msg00095.html I see, at present there is only a patch, no actual release containing the fix, that say the Debian provider would then distribute, I suppose. Sure hope microsecond differences seen by touch -r a b; stat -c

[EMAIL PROTECTED] overdose

On http://lists.gnu.org/archive/html/bug-coreutils/2004-03/msg00095.html look at all the [EMAIL PROTECTED] -u [EMAIL PROTECTED] --update ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

printf unicode documentation

You should mention that those \u things are Unicode here too $ man printf|grep -i unicode (finds none); not just on the Info page. BTW, in Info are you sure $ LC_CTYPE=zh_CN.big5 /usr/local/bin/printf \ '\u4e2d\u6587\n' > sample.txt does what you intend? $ LC_CTYPE=zh_CN.big5 /usr/bi

Re: [gnu.org #212217] [EMAIL PROTECTED] overdose

J> http://lists.gnu.org/spam.html yes, but if you look at http://lists.gnu.org/archive/html/bug-coreutils/2004-03/msg00095.html you'll see your algorithm has gotten out of hand. Not only email addresses are being changed, prompts too or whatever. Time to tighten your algorithm. J> If you subscr

Re: printf unicode documentation

> $ LC_CTYPE=zh_CN.big5 P> You need to have the proper locale support. Could it be that the Taiwanese mentioned on http://www.grassouille.org/blogmax/041009.html have made LC_CTYPE=zh_TW.Big5 proper and LC_CTYPE=zh_CN.big5 improper. All I know is that the former works and the latter doesn't here

ed: p and pppppp same

In ed(1), and p do the same thing, print one line. Compare - and - I would emit an error message. ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

cp -up forever

Perhaps fixed already? $ cp --version cp (coreutils) 5.2.1 $ touch g $ /bin/cp -upv g h `g' -> `h' $ /bin/cp -upv g h `g' -> `h' Once is enough. ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

changelog out of order

changelog is out of order here: $ zgrep ^2 /usr/share/doc/coreutils/changelog.gz|head 2002-07-01 Bernhard Rosenkraenzer <[EMAIL PROTECTED]> 2002-04-10 Andreas Gruenbacher <[EMAIL PROTECTED]> 2004-03-12 Jim Meyering <[EMAIL PROTECTED]> 2004-03-11 Jim Meyering <[EMAIL PROTECTED]> 2004-03-10 J

Re: cp -up forever

Here on debian sid coreutils 5.2.1-2 we see back digits are not tended to: # touch -r m o # stat -c %y m o 2004-10-10 01:56:36.561517778 +0800 2004-10-10 01:56:36.561517000 +0800 which must be the key to why cp -up will update repeatedly. Some lines from the strace you wanted: fstat64(4, {st_dev=m

uniq: exit status not documented enough

The uniq man page does not mention an exit status. Bad. The Info page says, An exit status of zero indicates success, and a nonzero value indicates failure. Oh, well as NAME uniq - remove duplicate lines from a sorted file therefore if it fails to remove duplicate lines from a sorted f

uniq: exit status not documented enough

The uniq man page does not mention an exit status. Bad. The Info page says, An exit status of zero indicates success, and a nonzero value indicates failure. Oh, well as NAME uniq - remove duplicate lines from a sorted file therefore if it fails to remove duplicate lines from a sorted f

Re: uniq: exit status not documented enough

P> * man/uniq.x: Change summary so that it doesn't imply that P> uniq writes to its input file. Problem reported by P> Dan Jacobson. Ah, indeed, it implied that too! Good snooping. However, as I was talking about exit codes, >> uniq - report or omit duplicate l

man pages must still work minimally

$ man ls --author print the author of each file $ ls --author nurd.txt Therefore the man page isn't accurate unless you place a statement at top that one must read the whole page first before using anything. You might as well say "see the Info page" at top instead of bottom.

du info: do say what's up with the : | jazz

On du info page: with this command : | dd bs=1 seek=`echo '2^31'|bc` of=big has an apparent size of 2 gigabytes, yet on most modern systems, You gotta say what's up with the : | jazz. Why not using if=/dev/null or something. People are curious. ___

mention why stat would show two blocks for one byte file

Nowhere on the stat or du info pages can the user figure out why $ echo>y; stat y File: `y' Size: 1 Blocks: 2 IO Block: 4096 regular file shows Blocks: 2. Ah, I know, stat is counting blocks by 512 bytes, but du counts them as 1024, which indeed must be how big they are

Re: It'd be great if you could submit a patch or two

Jim> It'd be great if you could submit a patch or two You see, I'm the fog headed user telling you what doesn't look clear from my perspective. Fog headed users by definition can't write sharp patches. For example you just changed "kilobytes" to KiB or something. I would have changed it the outer

wc: Invalid or incomplete multibyte or wide character

If not going to fix, at least the wc info page should mention something about, $ wc bla.tar.gz 2>&1|head -2 wc: bla.tar.gz:1: Invalid or incomplete multibyte or wide character wc: bla.tar.gz:2: Invalid or incomplete multibyte or wide character P.S., LC_CTYPE=zh_TW.Big5, wc (coreutils) 5.2.1, wc -l

Debian's at(1) is so bad, what does GNU use?

Constructive me says: Debian's at(1) is so bad, one can't even do $ at next year parse error. Last token seen: year Garbled time $ at now + 12 months #Sigh. Must use instead. No wonder. Not genuine GNU parts. Say, Stallman to the rescue. What do those cool GNU people use? Don't tell me they don't

Re: cp -up forever

P> The basic problem is that utimes() has only microsecond resolution; P> the kernel need to add a system call ("utimens()", say?) that P> supports nanosecond resolution. Dudes, I have discovered that after a reboot, (stat(1)) differences like Modify: 2004-12-10 23:28:07.877053000 +0800 Modify: 20

Re: Debian's at(1) is so bad, what does GNU use?

A> nohup sh -c "(sleep 100h; move-my-toes)" & Yeah, never rebooted where you live. Out with it, what at(1) command do they use at GNU? ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

basename dirname SEE ALSO

Can't basename's man page's SEE ALSO refer to dirname, and visa versa. BTW, on the info page 18.1 `basename': Strip directory and suffix from a file name is so long it wraps as it is in a big font. BTW, maybe add options to e.g., "show me just the last 3 dirs in $PWD". _

ls --indicator-style=dir

So fancy having ls `--indicator-style=WORD', but no way just to tell it we only want directories marked, not all the rest of the types. ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-coreutils

seq a c, --format. --equal-width

seq info says: `--format=FORMAT' Print all numbers using FORMAT; default `%g'. FORMAT must contain exactly one of the floating point output formats `%e', `%f', or `%g'. Yeah, well "exactly" scares one into thinking "%1.f" is not allowed unless they haven't lost hope and instead read

add fmt example output

In the fmt info page, examples would be worth a 1000 words with `--crown-margin', `--tagged-paragraph'. Mainly I wanted to turn short line LongLine short line into short line LongLine... . short line I.e., indentation after breaks. But no, there is no optio

man split should mention default split size

Man split should mention default split size, even though Info does. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

date --help sends one digging RFCs

man date and date --help have got to be kidding saying things like -R, --rfc-2822 output RFC-2822 compliant date string whereupon we have to go looking up what RFC-2822 compliant date strings look like. Make sure to show what they look like right there. _

ls -l --no-total

Did I mention ls should have a --no-total option to remove those annoying total 1120 without needing to pipe to a filter. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: date --help sends one digging RFCs

P> Consider that most people reading the docs will know the option exists P> and are simply confirming syntax, or won't care. Well I think --help at least could cut to the chase with actual samples. P> The info(1) documentation explains that the option is equivalent to the P> format string '%a, %

Re: date --help sends one digging RFCs

Eric> Instead of complaining, why not propose a patch? It doesn't even have to OK, maybe add an option that would show what all the flags are now, and in the current locale, $ date --examples-current which would give sort of like what $ set -- $(date --help| perl -anlwe 'next unless /./;$_=$F[0];

date zh_TW.Big5 +%P

You guys blew it for date +%P for locale zh_TW.Big5 $ date +%p%P -d 16 下午工午 $ date +%p%P 上午已午 The third character doesn't make sense to me both times. Just copying from %p would be safer. Or using nothing. Better ask a real Chinese. ___ Bug-coreutils ma

nohup basic documentation

$ man nohup If the info and nohup programs are properly installed at your site, the info coreutils nohup should give you access to the complete manual. So does info nohup. Users will wonder what is up. $ info nohup If standard output is a terminal, it is

ptx documentation needs at least one basic example

The tsort documentation has a nice example to get us started, tsort

chmod +++++++++x file

I found I could get away with chmod +x file. Perhaps catch it. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

rmdir -i

Hey no fair. rm has a -i, but rmdir doesn't. Yes, there are other ways to simulate it. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

chown man page: colon vs. dot

The chown man page talks about colon and dot, but only colon appears in examples. Add a clear statement about which is better, history etc. Wait! You say it on the info page, but not a peep on the man page. "See info page" not good enough. Add specific warning, like: Dot is old usage, see Info pag

nohup --no-output-file

Maybe add an option to make no nohup.out, so folks don't need to do nohup ... rm -f nohup.out And allow them to write to other places, not just nohup.out ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/

chown: say will write only if something needs to be changed

Please mention in the chown documentation when and if always, chown will only write to the disk if something needs to be changed! --- Begin Message --- On Tue 12 Apr 2005, Dan Jacobson wrote: > > Instead of > nohup chown -R proxy:proxy /var/cache/wwwoffle > Perhaps only chan

Re: rmdir -i

G> May be that's because rmdir works on ``empty'' directories. No point G> prompting. Some times we still want to be asked: $ rmdir -i dir4* dir?3 True, one could use features of xargs. Or we might want to alias to rmdir -i all day long for safety, empty or not. __

Re: chown man page: colon vs. dot

P> I think it's better not to mention dot insted. Dot is no longer P> portable (as per POSIX-2001). Well, mention that dot is deprecated, or else users can't tell if it is too old, or too new, when encountering it. ___ Bug-coreutils mailing list Bug-c

touch -d 20000000

What's the big idea of letting me use invalid dates? $ touch -d 2000 k $ ls -og k -rw-r--r-- 1 0 1999-11-30 00:00 k ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

seq 0 10 100|sed 1d

seq should have some more options so one wouldn't have to use sed here: $ seq 0 10 100|sed 1d ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

flag for one second timestamp comparison granularity

Perhaps add a flag to cp, find, etc. to reduce time comparisons to only one second granularity, as depending on the device mounted, or if we have since rebooted, times that should be the same can be reported back differently by the operating system. Or at least add a warning on man and Info pages.

Re: flag for one second timestamp comparison granularity

Well, I was just miffed that one can do $ while cp -u ... which in some situations will never stop. J> why stop at one second? The MS-DOS FAT filesystem has a two-second J> granularity Ah, no wonder. Ok, --granularity=2... ___ Bug-coreutils mailing li

no ptx example

Please include a little example with ptx, like you do for tsort. $ echo -e 'A 1\nB 2\nC 3'|ptx A 1 B 2 C 3 A 1 B 2 C 3 A 1 B 2 C 3 And below it explain what's going on. ___

head, tail: SEE ALSO dd(1)

Better mention dd here as an aside, else with just head and tail, how is one to 'output all but the first 906 bytes of a file'? 5 Output of parts of files ** These commands output pieces of the input. * Menu: * head invocation:: Output the first part of files

stty -F should cause an error

stty -F with no argument should cause an error, or the man page should say what it does. P.S., `-F DEVICE' `--file=DEVICE' Set the line opened by the filename specified in DEVICE instead of the tty line connected to standard input. This option is necessary because opening a POSIX

fold -s: add option for variable spaces at beginning

In case fold -s hasn't been enhanced since 5.2.1: Unhappy with wasted spaces at the end of each line, and no variable choice of how many spaces at the beginning of each continuation line, $ tr \\n ' ' http://lists.gnu.org/mailman/listinfo/bug-coreutils

install -d should bomb out if any args are regular files

This should bomb out right away, $ install -d /var/lib/dpkg/status /tmp/var/lib/dpkg/status install: `/var/lib/dpkg/status' exists but is not a directory instead of still creating /tmp/var/lib/dpkg/status. Also the documentation is not clear about what if any of the arguments already exist. ___

ls -L should say just what file doesn't exist

# ls -l ksyms.8.gz lrwxrwxrwx 1 root root 19 2005-08-14 02:36 ksyms.8.gz -> ksyms.modutils.8.gz # ls -L ksyms.8.gz ls: ksyms.8.gz: No such file or directory Shouldn't that message be more like the following's?: # ls ksyms.modutils.8.gz ls: ksyms.modutils.8.gz: No such file or directory ls (core

Re: ls -L should say just what file doesn't exist

Not sure if this is related: $ ls -og ??; grep a ?? lrwxrwxrwx 1 2 2005-11-18 07:08 xx -> yy grep: xx: No such file or directory User thinks: the problem is really "grep: yy: No such file or directory", and that might be a better message. Same with many other commands other than grep. _

Bug#344577: uniq -W gone with no trace

Package: coreutils Version: 5.93-5 Severity: normal File: /usr/bin/uniq What happened to uniq -W? Now it is not allowed. How is one to only compare on the first field anymore? I did find in the docs some hint: * Remove some ancient debian-specific patches - no more field seperator option to

Re: Bug#344577 acknowledged by developer (Re: Bug#344577: uniq -W gone with no trace)

m> Yup, it's gone. There was a note in README.Debian that it should be m> avoided. Please put notes on the man and Info pages about anything that will go away in the future. I had only used -W for three days after reading about it on the man page before it disappeared upon upgrade. _

sort -b also ignores tabs

sort -b not only ignores blanks, but also tabs. Mention this in the docs. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

date -I now undocumented

Is date -I still documented in info? $ info date 2>&-|col -b|wc 4433172 19847 $ info date 2>&-|col -b|grep -- -I|wc 0 0 0 Not here either: $ man date|col -b|grep -- -I $ date --help|grep -- -I $ date -I 2006-01-22 If deprecated then still say so. P.S., maybe just "date

Re: date -I now undocumented

Well I don't suppose we will ever see the word "deprecated" in any of your Info or man pages, even though it is part of good software practices. Apparently the GNU policy is, first an item silently disappears from a man or info page, then later the functionality is removed from the binary. Or eve

fold --spaces-have-priority-over-width wishlist.

fold has: `-s' `--spaces' Break at word boundaries: the line is broken after the last blank before the maximum line length. If the line contains no such blanks, the line is broken at the maximum line length as usual. Could add a switch to make --spaces have priority over width, guar

fold --break-chars=',. '

$ man fold -s, --spaces break at spaces How frustrating not to be able to tell it that breaking at commas is also OK. There should be an option to tell it what characters are OK to break at. Even perhaps a regexp. ___ Bug-coreutils

Bug#353909: sort: list all environmental factors

Package: coreutils Version: 5.93-5 Severity: minor File: /usr/bin/sort In this message *** WARNING *** The locale specified by the environment affects sort order. Set LC_ALL=C to get the traditional sort order that uses native byte values. The word "environment" must not

Bug#353911: md5sum --check checks only if _all_ are bad

Package: coreutils Version: 5.93-5 Severity: minor File: /usr/bin/md5sum Tags: upstream The docs indeed say "if no valid line is found, `md5sum' exits with nonzero status." i.e., 9 bad lines are no big deal, all we need is one good line and we pass the so-called "--check"!!: $ md5sum test/*|s

Bug#354875: /bin/cp directory full vs. disk full messages

Package: coreutils Version: 5.93-5 Severity: normal File: /bin/cp Trying to copy a less than 1MB file to a half full 16MB flash card, I get: # cp xutils_6.9.0.dfsg.1-4_i386.deb /mnt/usb/pqi cp: cannot create regular file `/mnt/usb/pqi/xutils_6.9.0.dfsg.1-4_i386.deb': No space left on device # df

document that echo can't be given a NULL

No way to hand echo or /bin/echo a NULL. $ set a $'\x00' b $ echo $# 3 $ echo A$'\x01'B|wc -c 4 $ echo A$'\x00'B|wc -c 3 $ echo -n `echo -ne 000`|wc -c 0 BASH_VERSION='3.1.0(1)-release' At least the echo docs should say so. ___ Bug-coreutils mailin

install(1) mention stdin

The install(1) documentation should mention how to specify stdin. (Use /dev/stdin, "-" doesn't work.) e.g., install -T /dev/stdin $t <<\EOF worked. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

sort -i: say if " " is nonprinting

`-i' `--ignore-nonprinting' Ignore nonprinting characters. The `LC_CTYPE' locale determines character types. This option has no effect if the stronger `--dictionary-order' (`-d') option is also given. Say if " " is nonprinting. ___ Bug-

sleep args

Could check for e.g., sleep 4 5 ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

[Chet Ramey] Re: current input line lost on ^Z

bug-bash@gnu.org item related to cat? Dan Jacobson wrote: > Perhaps bad? > $ cat > p > bb > ccc^Z > $ something_else > $ fg > zzz > ^D > $ cat pr > bb > zzz > > "I was not finished composing line ccc w

Re: sleep args

OK, but document all this with examples on the info AND man pages, something in the usage message too. Yes, I now see the "...", but without an explanation, one cannot assume that args are added... And mention what is a GNU extension, and what is portable.

pound of flesh to see what date -R will print

$ date --help or man date: -R, --rfc-2822 output date and time in RFC 2822 format We must go look up the RFC and read it to find out what this format looks like. Or we must dig thru the long winded Info page. Or we must try it $ date -R Sun, 25 Jun 2006 02:35:21 +0800 OK, th

don't say uniq -D -c is meaningless

$ dmesg|sort|uniq -D -c uniq: printing all duplicated lines and repeat counts is meaningless Try `uniq --help' for more information. Meaningless for you, but just what I want: $ dmesg|sort|uniq -D|uniq -c 5 EXT3-fs: mounted filesystem with ordered data mode. 2 PCI: Hardcoded IRQ 14 fo

Re: sleep args

EB> Quoting from 'info sleep': EB> `sleep' pauses for an amount of time specified by the sum of the values EB> of the command line arguments. $ man sleep | grep -i argumentS | wc -l 0 EB> That's pretty clear to me. The --help output (and thus man pages) EB> are intentionally less verbose, since

Re: don't say uniq -D -c is meaningless

PB> You want `uniq -dc` OK, the message should mention that. PB> Adding -u to -d or -D just suppresses the last item of each group. PB> These options are meaningless anyway: PB> uniq -ud ≡ uniq's default mode of operation PB> uniq -uD ≡ cat Hope all that is documented. ___

pr -COLUMN vs. wide characters

Why doesn't the first line of this output line up? $ cat f f|env - pr -2 -T 一二三 123 一二三 123 b２ 00 b２ 00 Ｃ３Ｃ３ efg efg Same problem utf-8 or big5. It should line up on fixed

undocumented stty speeds

I am on a page of Info called Special, that must be related to stty. `N' Set the input and output speeds to N. N can be one of: 0 50 75 110 134 134.5 150 200 300 600 1200 1800 2400 4800 9600 19200 38400 `exta' `extb'. `exta' is the same as 19200; `extb' is the same as 38400.

can't understand csplit without examples

csplit info page: `N' Create an output file containing the input up to but not including line N (a positive integer). If followed by a repeat count, also create an output file containing the next N lines of the input file once for each repeat. Add an example. `/REGEXP/[OFFSET]

the ptx documentation contains no examples

The ptx documentation contains no examples. Show $ cat infile bla bla bla $ cat infile|ptx Else how can one get started? You added examples to the tsort docs but not ptx. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mai

warn of obsolete tail usage on the man page too

Perhaps also warn about obsolete thing on the man page too. $ info -w cor tail|xargs zgrep -ic obsolete 18 $ man tail|grep -ic obsolete 0 ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

fold not UTF-8 ready

Fold splits UTF-8 chars into their bytes and probably doesn't know about their display width either. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

install --hardlink

If `install' is similar to `cp', but allows you to control the attributes of destination files. It is typically used ... to copy programs into their destination directories. Then it is ripe for adding new functionality: --hardlink make hard links instead of copying (And maybe even --

stty: explain line discipline

In the stty Info page, mention what "line discipline" is all about. P.S., Man page: incomplete sentence: * [-]imaxbel beep and do not flush a full input buffer on a character ___ Bug-coreutils mailing list Bug-coreutils@gnu.org htt

Bug#394257: od -w parsing broken

X-debbugs-cc: bug-coreutils@gnu.org Tags: upstream Package: coreutils Version: 5.97-5 Severity: normal File: /usr/bin/od $ od --help|grep -- -w|tail By default, od uses -A o -t d2 -w 16. $ date|od -A o -t d2 -w 16 od: 16: No such file or directory #must use $ date|od -A o -t d2 -w16 ___

join(1) documentation

Regarding Info page 8.3 `join': Join lines on a common field However, as a GNU extension, if the input has no unpairable lines the sort order can be any order that considers two fields to be equal if and only if the sort comparison described above considers them to be equal. For example

uniq(1) documentation

Info 7.2 `uniq': Uniquify files: By default, `uniq' prints its input lines, except that it discards all but the first of adjacent repeated lines, so that no output lines are repeated. Optionally, it can instead discard lines that are not repeated, or all repeated lines.

cp -i: "sucker Holmes" questions

Seen on Debian coreutils 5.97-5: $ cp -i b a cp: overwrite `a', overriding mode 0644? y cp: cannot create regular file `a': Permission denied The message "overriding mode 0644?" does not drive home the real problem, which is a ownership problem I suppose, so the message could be improved.

no fair only at the end mentioning where the complete manual is

The GNU man pages have a big flaw, e.g., DESCRIPTION This manual page documents the GNU version of df. df displays the But only when the reader gets to the bottom of the page does he discover: SEE ALSO The full documentation for df is maintained as a Texinfo manual. I

sort -c --dont-poop-out-at-the-first-disorder

Gentlemen, consider a file with oh, three points of disorder. Well, $ sort -c timez1 sort: timez1:418: disorder: 1162082133 is great at finding the first one, but to find the other two one has to use ones brains. No fair. So there should be some --dont-poop-out-at-the-first-disorder option, to

Bug#398926: df gives wrong sizes for CDROM

Package: coreutils X-debbugs-cc: bug-coreutils@gnu.org Version: 5.97-5 Severity: normal File: /bin/df # mount /cdrom # df /cdrom Filesystem 1K-blocks Used Available Use% Mounted on /dev/scd045684 45684 0 100% /cdrom # df /cdrom Filesystem 1K-blo

wc: billion "incomplete multibyte" warnings

Did anyone ever mention that a billion $ bla_bla|gzip|wc 2>&1|head -n 1 wc: standard input:1: Invalid or incomplete multibyte or wide character $ bla_bla|gzip|wc 2>&1|wc 3083073 22634 (OK, not a billion, but just the same as far as one's terminal buffer is concerned) is more than enough t

date: Chinese: confusing on Sundays

Please forward this to whoever. A funny thing happens on Sundays if you are Chinese. $ LC_CTYPE=zh_TW.utf8 date -d sunday 日 12月 10 00:00:00 CST 2006 The problem occurs because the word 日 means "Sunday" and also "day" in Chinese. Therefore 日 12月 10 00:00:00 CST 2006 looks like Day 12Month 10 00:00

tocuh: protect ones' self against ones' self

touch Info page says: If changing both the access and modification times to the current time, `touch' can change the timestamps for files that the user running it does not own but has write permission for. Otherwise, the user must own the files. Please reword. "Otherwise"=not both

dd blocks/bytes at a time

On both the dd man and Info pages, we see count=BLOCKS copy only BLOCKS input blocks OK, but one must use ones brain, heavens forbid, to figure out that e.g., these bs=BYTES force ibs=BYTES and obs=BYTES ibs=BYTES read BYTES bytes at

Re: [PATCH] Re: dd blocks/bytes at a time

OD> Here is a patch that may change this. Looks good. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

pr considers bytes not presentation width

Double width characters don't line up with pr or pr|expand. LC_ALL doesn't change things. Perhaps it is counting Unicode as bytes, perhaps it is thinking every character is one column wide. $ set 001 台中-谷關 東勢-興中山莊-台中 $ pr -mT $@|head -n 6 *{{b|仁友東站}} *{{b|台中火車站}}

  1   2   3   4   >