Re: chown should catch null owner:group

LW> "chown -R ." gave an error Try DJ> chown -R . file which should emit "Holmes, you think you are changing the owner of FILE to be the same as the owner of ".", but you have actually typed something else (-R means recursive) which is an absolute error, about which the new improved chown command w

Re: chown should catch null owner:group

EB> `:' EB> ~ If only a colon is given, or if NEW-OWNER is empty, neither the EB> ~ owner nor the group is changed. OK, I'll drop my case, but please add a comment to this documentation about "why" or "who knows why?" or the motivation behind or uses of, this case. Perhaps "just to be ort

stat -f output standpoint

$ { stat .; stat -f .;}|grep File File: `.' File: "." For the latter, shouldn't you say Filesystem of "." or File: "/dev/hdz" Else it's like your still talking about just the argument and not its filesystem. stat (GNU coreutils) 6.10. (P.S., you might enjoy writing `' instead of "", but it j

stat info ls "total"

On the "stat" info page, at `--apparent-size' Print apparent sizes, rather than disk usage. The apparent size of a file is the number of bytes reported by `wc -c' on regular files, or more generally, `ls -l --block-size=1' or `stat ^the "total" line af

stat --apparent-size

Also note that many people who are looking for --apparent-size style facilities are in fact looking for ways to find out which files have holes in them. The closest one can get to doing that might be something like $ find -type f -printf %S\\t%p\\n If there is a sure fire way, do add a note about i

cp -u vs. vfat's TWO seconds

Bad news fellows, regarding: `-u' `--update' Do not copy a non-directory that has an existing destination with the same or newer modification time. If time stamps are being preserved, the comparison is to the source time stamp truncated to the resolutions of the destin

Re: cp -u vs. vfat's TWO seconds

JM> It'd be great if you would suggest wording to document this discrepancy. The wording is fine as is. The problem is that you don't act according to your wording. You think "truncate fractional seconds, using one-second buckets to compare", whereas you need to use two-second buckets to compare

Re: cp -u vs. vfat's TWO seconds

JM> - document a subtle limitation encountered when using a losing file system It's the Lingua Franca of USB filesystem where I live. You change your comparison from Modify: 2008-04-03 05:45:22.7 to one second buckets Modify: 2008-04-03 05:45:22 so it should be just as easy to add a two

Re: cp -u vs. vfat's TWO seconds

All I know is your program is guilty of conspiracy to wear out people's USB flash cards. If FAT is detected, just run source and destination times thru a chopper like $ m=$(date +%s); echo -n $m--\>; expr $m / 2 \* 2 1207175575-->1207175574 and cp -u will never blow it again, innocent of any futur

ls: sort on -s

I'm at the emacs' dired prompt, ls switches (must contain -l): -ogsS when I realized that -S is not good enough. What I want is an additional way to sort: on the -s sizes! > Just do ls -sog|sort -nr I hear you saying. But I can't. This is dired I'm in. _

Re: ls: sort on -s

> "JY" == James Youngman <[EMAIL PROTECTED]> writes: JY> On Wed, Apr 9, 2008 at 4:21 AM, <[EMAIL PROTECTED]> wrote: >> I'm at the emacs' dired prompt, >> ls switches (must contain -l): -ogsS >> when I realized that -S is not good enough. >> What I want is an additional way to sort: on the -s

Re: cp -up forever

Fellas, in http://bugs.debian.org/276500 m> There is a new syscall in 2.6.22, utimensat. It gets a "struct timespec" m> which allows nanosecond resolution. That means you can now fix the difference in $ touch m; touch -r m n; stat -c %y m n 2008-06-24 06:13:24.106160298 +0800 2008-06-24 06:13:24.10

document stty -g code positions

In (info "(coreutils)stty invocation"), please mention what all the secret codes in stty -g (--save) are. One could see e.g., right away that position 15 is different on my mom's terminal, but what stty setting is position 15, one asks? Otherwise one has to do e.g., COLUMNS=1 stty -a > /tmp/ww CO

ls -s but sorted

ls man page says -s, --size print the size of each file, in blocks -S sort by file size but to sort by block size (not always the same as file size due to files with holes), one must do ls -s|sort -n ___ Bug-coreutils m

Re: ls -s but sorted

JY> What are you suggesting should be changed? There is no way to get any order into these rectangles I cropped from your reply: ~/tm tota 104K 12K 32K ~/tm tota 12 104 32 One must resort to an external program to get them in order. You only offer -S sorting, but we people trying to weed out

terrible Unicode shattering fold(1) command

Problem 1: Here we see fold -s busy busting apart UTF-8 characters again still. Every third chop falls on a boundary, so is lucky. No, I did not use `--bytes'. The result is the same as if I did anyway! Problem 2: Also, when the critical chunk moves past the chopper blade, and we now start chop

Re: terrible Unicode shattering fold(1) command

>> `--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. OR the line is not broken <-- new option, please add. JY> FWIW, that is har

date validator

Regarding some RISKS postings that bear not so standard Dates, causing some browsing systems to read them as Jan 1 1970, etc., > "R" == RISKS List Owner <[EMAIL PROTECTED]> writes: R> How do we address this? We need to get every mailer in the world R> compliant... Well, we could pump all da

Uniq is so tilted to "first"

Uniq is so tilted to "first" $ man uniq|grep compar.*first avoid comparing the first N fields avoid comparing the first N characters $ man uniq|grep -c last 0 All so inflexible. There should be a more general way with ranges. ___

test -t

On (info "(coreutils)File type tests", and test(1) man page, we see `-t FD' True if FD is a file descriptor that is associated with a terminal. Well please mention what happens if FD is omitted: $ test -t The answer is it always returns true, no matter what. Test with $ echo 'set -x; for

date -u vs. CST

$ for i in E C M P; do for i in ${i}ST; do echo -n $i:; date -ud "7:00 $i"; done; done EST:Wed Sep 3 12:00:00 UTC 2008 CST:Wed Sep 3 13:00:00 UTC 2008 MST:Wed Sep 3 14:00:00 UTC 2008 PST:Wed Sep 3 15:00:00 UTC 2008 $ for i in E C M P; do for i in ${i}ST; do echo -n $i:; date -d "7:00 $i"; do

stat(1) badly needs flag to just print name of the symlink

Is it true that there is no stat(1) flag to just print the link name? All one can find is %N - Quoted file name with dereference if symbolic link $ stat -c %N s1mp3.backup `s1mp3.backup' -> `/mnt/extra10/s1mp3' meaning the user must be dragged over the coals to do $ stat -c %N s1mp3.backup |perl -F

Re: stat(1) badly needs flag to just print name of the symlink

EB> What's wrong with readlink(1)? OK, I will let you off the hook if you enhance the stat(1) man page to please say something like: %N Quoted file name with dereference if symbolic link For just the dereference name, see readlink(1). _

quoted-printable en/decoder, to complement base64

There should be a quoted-printable en/decoder, to complement base64. Let's see what I was using for all these. #!/bin/sh -e #jidanni *** replacement for mime-codecs package *** case $0 in *qp-encode)perl -MMIME::QuotedPrint -wne 'print encode_qp($_)';; *qp-decode)

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

PS> Otherwise I'd like to hear the submitters opinion as well. The submitter leaves it all in your hands as I am not as sharp as I used to be. Thanks. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreut

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

JM> It should process every line. JM> My question was whether to emit a diagnostic for each _malformed_ line, JM> or just for the first or maybe the first few. Like cmp(1) bail out if any trouble perhaps, but have options for fuller digging/reports. OK, never mind... I leave it in your hands. __

stty doc 'enhancements'

On (info "(coreutils)stty invocation") say what you mean by Input Settings and Output Settings. I.e., what you type into the terminal and then goes into... what is sent from the computer to your terminal...?? After `iuclc' Translate uppercase characters to lowercase. Non-POSIX. May be

git-diff shows none, even before ./bootstrap

Following the instructions in Reading README-hacking, $ ./bootstrap Error: 'autoconf' not found ... Well, rather then installing all those boring packages, I just skipped down to > At this point, there should be no difference between your local copy, > and the GIT master copy: >$ git diff

say in ChangeLog-2008 why dead

In HACKING: No more ChangeLog files === Do not modify any of the ChangeLog files in coreutils. Starting in 2008, the policy changed. OK, but you better put a note about that at the top of ChangeLog-2008, else it looks like somebody died. __

better figure out a paperless copyright assignment method

Copyright assignment ...of an actual sheet of paper... Sorry, I'm on a non-USA Pacific island mountaintop with no paper business... anyway, got pictures of RMS and me on my website, so he'll have to vouch for me. ___ Bug-coreuti

HACKING doc git 3rd possiblity

In HACKING If you have made *no* changes: git pull If you *have* made changes and committed them to "master", do this: git fetch git rebase origin OK, but add If you *have* made changes but *have not* committed them to "master", do this: As to what "this" should

[PATCH] stty doc enhancements

--- doc/coreutils.texi | 12 +--- 1 files changed, 9 insertions(+), 3 deletions(-) diff --git a/doc/coreutils.texi b/doc/coreutils.texi index 49aa16d..020dc51 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -11919,6 +11919,8 @@ Enable RTS/CTS flow control. n...@acronym{posi

Re: [PATCH] stty doc enhancements

All good except: PB> How about: PB> These settings control operations on data received from the terminal. PB> These settings control operations on data sent to the terminal. Remember that you need to locate the user between the two ends of something... One can't just imply. In each sentence you nee

Re: better figure out a paperless copyright assignment method

Wait a second, when making a Wikipedia editing contribution we just click on a box below some licence statement. Why can't you guys use that method? ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: better figure out a paperless copyright assignment method

> "EB" == Eric Blake writes: EB> According to jida...@jidanni.org on 12/18/2008 9:55 PM: >> Wait a second, when making a Wikipedia editing contribution we just >> click on a box below some licence statement. Why can't you guys use >> that method? EB> Why are you asking us, when we can't do a

pathchk info page should mention other leading brand

$ info cor pathchk When I read this info page the question that one asks is "What about Windows? I want to know if I zip up some files and give them to my friend, will there be some problem when he unzips them on Windows?" So perhaps add after 3. A file name contains a character outside the

Re: pathchk info page should mention other leading brand

OK, but I would still say "By portability we are not talking about portability to other operating systems!" ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

No more "Your first commit: the quick and dirty way"

In the file HACKING, please remove the "Your first commit: the quick and dirty way". Just directly mention the right way, "Make your changes on a private "topic" branch" It only costs the user a couple more commands. Else you are starting many first time git users on the wrong foot; days of miser

document sort -uf[r]

Regarding sort: `-f' `--ignore-case' Fold lowercase characters into the equivalent uppercase characters when comparing so that, for example, `b' and `B' sort as equal. The `LC_CTYPE' locale determines character types. OK, but also document this: $ echo -e 'A\na'|sort -uf A $ echo -e

Date can dish it out, but not parse it back in

Date can dish it out, but not parse it back in, for other languages: $ date 五 1月 16 00:49:11 CST 2009 $ date|date -f - 五 1月 16 00:00:00 CST 2009 $ LC_ALL=C date|date -f - 五 1月 16 00:49:26 CST 2009 $ locale LANG=zh_TW.UTF-8 LC_CTYPE=zh_TW.UTF-8 LC_NUMERIC="zh_TW.UTF-8" LC_TIME="zh_TW.UTF-8" LC_CO

Re: Date can dish it out, but not parse it back in

OK, better add after `-d DATESTR' `--date=DATESTR' Display the date and time specified in DATESTR instead of the current date and time. DATESTR can be in almost any common format. That it wants ASCII... P.S., nobody saw my http://lists.gnu.org/archive/html/bug-coreutils/2009-01/msg

[PATCH] document sort --ignore-case --unique interaction

Signed-off-by: jidanni --- doc/coreutils.texi |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/doc/coreutils.texi b/doc/coreutils.texi index d8df107..06b259c 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -3742,6 +3742,10 @@ is a space or a tab, but the

Subject: [PATCH] date doc: warn at -d about LC_TIME

We also warn here about LC_TIME, so the user will know even if he doesn't look in the @xref{Date input formats}. Signed-off-by: jidanni --- doc/coreutils.texi |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/doc/coreutils.texi b/doc/coreutils.texi index d8

coreutils.texi too big

Gentlemen, it dawned on me. coreutils.texi is too big, from a source code management point of view. It should be broken down into logical parts, one for stty, one for sort, etc. Then you can pull it all together via @includes. Anyway, it makes no sense for e.g., edits to stty invocation to conflict

Re: coreutils.texi too big

EB> Care to submit a patch? (To tell you the truth I never tested my previous patches worked in textinfo or texinfo or whatever it's called :-) I just did monkey see monkey do) as you see somebody has to be in the ideas department, passing on ideas to the implementation experts... ___

[PATCH, resend] document sort --ignore-case --unique interaction

Signed-off-by: jidanni --- No reply last time so resending. doc/coreutils.texi |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/doc/coreutils.texi b/doc/coreutils.texi index d8df107..06b259c 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -3742,6 +3742,10

[PATCH,resend] date doc: warn at -d about LC_TIME

We also warn here about LC_TIME, so the user will know even if he doesn't look in the @xref{Date input formats}. Signed-off-by: jidanni --- Also no reply last time. Resending. doc/coreutils.texi |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/doc/coreutils.t

Re: ls -s documentation misleading

By the way, turning to -l, looking high and low on (info "(coreutils)What information is listed") doesn't say why ls follows symlinks, but ls -l doesn't: $ ls q f $ ls -l q lrwxrwxrwx 1 jidanni jidanni 1 2009-02-22 01:57 q -> z (Made with:) $ mkdir z

must use cp && rm as mv has no --no-preserve

Gentlemen, I have discovered I must use cp && rm as mv has no --no-preserve. # touch k; mv k /cf mv: failed to preserve ownership for `/cf/k': Operation not permitted # touch k; cp -a --no-preserve=owner k /cf && rm k You see, moving to VFAT, one will get that message under different mount owners

ls -l --show-me-each-link-in-the-symlink-chain

ls -l shows you the start of the symlink chain, ls -lL shows you the end of the symlink chain, but to see each link, one needs many ls -l's. There ought to be an option to see each link. Sure, there is usually just one link, but sometimes there is more.

Re: ls -l --show-me-each-link-in-the-symlink-chain

> "EB" == Eric Blake writes: EB> According to jida...@jidanni.org on 3/25/2009 12:23 PM: >> ls -l shows you the start of the symlink chain, >> ls -lL shows you the end of the symlink chain, >> but to see each link, one needs many ls -l's. >> There ought to be an option to see each link. E

say when comm separator disappears

In (info "(coreutils)comm invocation"), after: With no options, `comm' produces three-column output. Column one contains lines unique to FILE1, column two contains lines unique to FILE2, and column three contains lines common to both files. Columns are separated by a single TAB ch

bomb out quicker if cannot set date

$ date -s date: cannot set date: Operation not permitted Wed May 20 11:11:00 CST 2009 OK, then please don't print out that date afterward. Just bomb out. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bu

Savannah report new bug link not obvious

Logged in to https://savannah.gnu.org/ the user cannot find the link to "report a new bug". ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

document or fix dangers of sort -u + any other option

Please fix the third command, $ echo -e 'a1\nb2\nc3\nb2'|sort -n|sort -u a1 b2 c3 $ echo -e 'a1\nb2\nc3\nb2'|sort -u|sort -n a1 b2 c3 $ echo -e 'a1\nb2\nc3\nb2'|sort -nu a1 or warn right there on the man page. Sure, you say -u, --unique with -c, check for strict ordering; w

Re: Savannah report new bug link not obvious

> "GS" == Giuseppe Scrivano writes: GS> jida...@jidanni.org writes: >> Logged in to https://savannah.gnu.org/ >> the user cannot find the link to "report a new bug". GS> Is https://savannah.gnu.org/bugs/?func=additem&group=coreutils the page GS> you are looking for? Ah, indeed it is. OK, all

Re: Savannah report new bug link not obvious

EB> Actually, for coreutils, we are just as happy with email bug reports (as Well do leave a path for those of us who have been toiled-trained by e.g., Bugzilla that the only real report is a browser generated report, and can't find the "Pavlov's dogs lever", http://en.wikipedia.org/wiki/Classical

Re: Bug#505927: just use the date(1) -d library instead of your own poorer date parser

> Regarding http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505927 > "BSB" == Bernd Siggy Brentrup writes: BSB> Hi, BSB> I'm currently evaluating at's wishlist bugs for my 'at' replacement BSB> 'at-ng' which is a complete rewrite from scratch. Uh oh, "at no good"? :-) BSB> On Mon, Nov

Re: Bug#505927: just use the date(1) -d library instead of your own poorer date parser

>> >> However to get at to accept such a date, one needs: >> >> $ at -v $(date --rfc-3339=date -d 'now + 5 years + 11 months') >> >> Fri Oct 17 03:56:00 2014 >> >> warning: commands will be executed using /bin/sh B'B> How do you like these: B'B> at-ng/build% ./at now + 5 years + 11 months B'B> Job

Re: Bug#505927: just use the date(1) -d library instead of your own poorer date parser

>>>>> "BSB" == Bernd Siggy Brentrup writes: BSB> Hi jidanni, BSB> I'm extremely angry about you forwarding my findings to the BSB> Debian BTS. Sorry. I just try to increase people's networking, and assumed the bug number, which I saw in the Subject,

Bug#545721: info: No menu item `mktemp invocation' in node `(coreutils.info.gz)Top'.

X-debbugs-cc: bug-coreutils@gnu.org Package: coreutils Version: 7.5-3 Severity: minor $ man mktemp|col -b|grep -C 3 'info coreutils' The full documentation for mktemp is maintained as a Texinfo manual. If the info and mktemp programs are prop erly installed at your site, the comm

quoted-printable [--decode]: it's time

OK, now that there is a base64(1) command, I could have sworn I also saw a quoted-printable command too [or else I wouldn't have deleted mine so fast :-(]. OK, I restored mine $ cat bin/qp-decode #!/bin/sh -e #jidanni *** replacement for mime-codecs package *** case $0 in *qp-encode)

Re: quoted-printable [--decode]: it's time

> "JM" == Jim Meyering writes: JM> GNU recode does that: JM> $ printf '\0\1'|recode ../QP Ah ha, then checkmate, $ recode -l|grep -i base64 /Base64 64 b64 I.e., you must either 1. Make a separate quoted-printable(1) command too, just to be fair. 2. Leave a note on the base64(1) man page

mv -v, cp -v messages should be different

Gentlemen, I object. The messages for these two commands should be different. $ cp -v f g `f' -> `g' $ mv -v f g `f' -> `g' Exactly how different etc. I leave up to you. Maybe even just => for the latter instead of ->.

Bug#565218: info boilerplate on man page gives only the hard way

X-debbugs-cc: bug-coreutils@gnu.org Package: coreutils Version: 8.1-1 Severity: wishlist We see many The full documentation for WHATEVER is maintained as a Texinfo manual. If the info and WHATEVER programs are properly installed at your site, the command info c

Re: Bug#565218: info boilerplate on man page gives only the hard way

> "MS" == Michael Stone writes: MS> On Thu, Jan 14, 2010 at 06:00:17AM +0800, jida...@jidanni.org wrote: >> Well, it turns out that we find we often can also just do >> $ info WHATEVER MS> Yes, that's why it used to say that. But if something goes wrong with MS> info, that invocation will fa

tee|tee|tee

The tee(1) documents fail to say what happens when tee is given no arguments. Do say what is going on in $ echo o|tee|tee|tee o Also there is a Info reference to (bashref), but here on Debian there is no such match in apt-file(1).

Re: tee|tee|tee

> "GS" == Giuseppe Scrivano writes: GS> jida...@jidanni.org writes: >> The tee(1) documents fail to say what happens when tee is given no >> arguments. Do say what is going on in >> $ echo o|tee|tee|tee GS> "The `tee' command copies standard input to standard output and also to GS> any files

expr say "non integer argument"

$ expr 3.1 + 3 expr: non-numeric argument <---say "non integer argument" $ expr 3.1 + 3b expr: non-numeric argument

Re: expr say "non integer argument"

> "CFAJ" == Chris F A Johnson writes: CFAJ> On Thu, 18 Feb 2010, jida...@jidanni.org wrote: >> $ expr 3.1 + 3 >> expr: non-numeric argument <---say "non integer argument" >> $ expr 3.1 + 3b >> expr: non-numeric argument CFAJ>The expr command's arithmetic only works with integers. Yes CFA

Re: expr say "non integer argument"

EB> jidanni, it would be a two-line patch to expr.c. Would you care to write EB> such a patch, rather than just complaining? It would be much more efficient for me to just play the role of the bug reporter here trust me. Thanks.

Re: expr say "non integer argument"

CFAJ> That'll teach me to post early in the morning! The problem is that you live in the incorrect timezone :-|

Re: expr say "non integer argument"

$ diff --git diff: unrecognized option '--git'<--see my next email coming soon. $ dlocate src/expr.c|wc 0 0 0 Actually at one point I was much more involved. http://article.gmane.org/gmane.comp.version-control.git/103400 However today its bash: git: command not found for me, as

diff "--git"

$ diff --git diff: unrecognized option '--git' I think diff should say at this point "real diff, at least up to year 2010, does not have a --git option, you are probably getting that idea from git output" or something. Or ask those git pros for a patch to give diff a --git option, or tell them th

Re: diff "--git"

AMS> That is what it says, though not in so many words. Having an option AMS> for each VS would really be a headache (SCCS, RCS, CVS, hg, darcs, AMS> bzr, tla, git, ...). Well all I know is we then harangue the system administrator for not installing the latest diff that the other guys are alread

Re: -readable by who

Gentlemen, some of these are clearer than man test or (info "(coreutils) Access permission tests") bash$ help test|grep you -r FILETrue if file is readable by you. -w FILETrue if the file is writable by you. -x FILETrue if the file is executable by you.

you are not going to be able to sort this by the fifth field.

Try as you might, there is no way you are going to sort by this field, $ LC_CTYPE=zh_TW.UTF-8 w3m -dump \ http://www.tcb-bank.com.tw/tcb/servicesloc/atm_location/taichung_county_atm.htm | perl -anlwe 'print $F[4] if exists $F[4]'|LC_CTYPE=C sort without ripping it out of the table first using

say that cut can't handle more than one field demarcator

On (info "(coreutils) cut invocation") please add: cut has no way to specify a group of blanks as a field demarcator. If you want that, use perl -a. Also use perl's split if you want regexp demarcators, etc. If that is indeed the case.

Re: you are not going to be able to sort this by the fifth field.

Thanks. I see I neglected the -b. On the info page in the `--field-separator=SEPARATOR' discussion, do mention the effects of -b on ' foo' etc. PB> $ LC_CTYPE=C sort --debug -sb -k5,5 < taichung_county_atm.htm (Use .txt, not .htms in examples.) Anyway, your --debug stuff would be clearer with just

Re: you are not going to be able to sort this by the fifth field.

EB> Except that you can specify overlapping keys. I find the idea of multiple EB> separate lines of underscores, one per key, much easier to follow in OK, any --debug=... is better than nothing.

Re: say that cut can't handle more than one field demarcator

> tr -s '[:blank:]' '\t' | cut -f5 And perhaps mention less painful tr -s \ \\t | cut -f5 and perl -anwle 'print $F[4]' if the user's input permits such simplification...

bug#7502: wc --verbose should say xx lines, yy words, zz characters

Idea: new option: --verbose $ wc --verbose should say xx lines, yy words, zz characters or xx lines yy words zz characters etc. With TAB separator too.

bug#7529: Bug#605639: deal better with different filesystem timestamp resolutions

7;t working too much/well, $ touch /tmp/f $ /bin/cp -avu /tmp/f . `/tmp/f' -> `./f' $ /bin/cp -avu /tmp/f . `/tmp/f' -> `./f' $ /bin/cp -avu /tmp/f . `/tmp/f' -> `./f' $ ls -l --full-time f /tmp/f -rw-r--r-- 1 jidanni jidanni 0 2010-12-02 08:25:47.682527260 +

bug#7568: stat 'i\i' shows 'i\\i'

stat 'i\i' shows 'i\\i'. Backspaces in filenames are doubled. stat (GNU coreutils) 8.5

bug#7618: man mktemp/[deprecated] clarification

man mktemp -p DIR use DIR as a prefix; implies -t [deprecated] -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] It is not clear what is deprecated, -p, or

bug#7877: sleep takes undocumented hex args

The documentation doesn't say that one can also use hex args: $ time /bin/sleep 0x10 real0m16.007s However not octal args: $ time /bin/sleep 010 real0m10.003s Maybe say how too.

bug#7877: sleep takes undocumented hex args

You see I was trying to make very special arguments to sleep so that I can make sure to kill the one I want pkill -u jidanni -fx sleep\ 22 It is not clear if that will still work. Maybe the man/info page should say a regexp that matches all valid args.

bug#7877: sleep 5 -4

$ sleep 5 -4 sleep: invalid option -- '4' $ sleep -- 5 -4 sleep: invalid time interval `-4' No fair prejudicing negative numbers. At least document it. 'However, GNU `sleep' accepts arbitrary floating point numbers (using a period before any fractional digits).' is what it says on Debian.

bug#7877: sleep 5 -4

> "PE" == Paul Eggert writes: PE> (Have I written enough to tempt ... to extend 'sleep' PE> to allow negative numbers? :-) Right you are young man. We here at NerdLabs already use $ sleep -- -100 to give us a few moments to go back and correct errors. But due to National Security, that's all

bug#8241: Bug#618009: date: invalid date `TZ="America/Chicago" now' but Europe/Paris OK

Package: coreutils Version: 8.5-1 File: /bin/date X-debbugs-cc: bug-coreutils@gnu.org for i in Asia/Taipei America/Chicago America/New_York Europe/Paris do for j in monday now yesterday today tomorrow 12pm do echo TZ=\"$i\" $j; done; done|date -f - gives date: invalid date `TZ="America/Chicag

Re: mv: overwrite `/etc/lilo.conf', overriding mode 0644?

J> Thanks for the bug report, but 5.97 is very close to a year old. J> You're wasting your time testing it, I think, because many changes J> have been made since then. Please try a recent version of coreutils. J> (More generally, before reporting a bug in any piece of software, it J> is advisabel

who(1) shows more than one user on the same terminal

Is it normal to see two users on the same tty? $ who jidanni pts/0 ... ralphpts/0 ... jim pts/1 ... $ ls -l /dev/pts/0 crw--w 1 jidanni tty 136, 0 2007-08-17 00:58 /dev/pts/0 The administrator (Dreamhost) says > You could potentially see many more than that at any given t

Re: /usr/bin/test message forgets newline

JM> [note that only "[" accepts an OPTION. ] Ah, fine print. Land mine. JM> DESCRIPTION JM>Exit with the status determined by EXPRESSION. perhaps repeat the [note that only "[" accepts an OPTION. ] here. JM>--help display this help and exit JM>--version JM> o

/usr/bin/test message forgets newline

/usr/bin/test neglects adding the trailing newline for this message at least: # /usr/bin/test -d 1 2 3 2>&1|od -c 000 / u s r / b i n / t e s t : e 020 x t r a a r g u m e n t ` 2 040 ' 041 P.S., $ /usr/bin/te

wacko LC_ALL=zh_TW.utf8 egrep -i

$ printf Me\\nji\\n|LC_ALL=zh_TW.utf8 egrepMe\|ji Me ji $ printf Me\\nji\\n|LC_ALL=zh_TW.utf8 egrep -i Me\|ji ji $ printf Me\\nji\\n|LC_ALL=zh_TW.utf8 egrep -i Me Me $ printf Me\\nji\\n|LC_ALL=zh_TW.utf8 egrep -i me\|ji ji GNU grep 2.5.3 ___ Bug-co

fold UTF ready?

fold (GNU coreutils) 5.97 * counts bytes, not columns, even without -b * has no compassion for multibyte chars, turning UTF-8 into illegal sequences. export LC_ALL=zh_TW.utf8 echo 不准作台灣人|fold --help echo 不准作台灣人|fold -w 2 echo 不准作台灣人|fold -w 3 echo 不准 作台灣人|fold -w 3 echo 不准 作 台灣人|fold -w 3 echo 不准 作

Re: fold UTF ready?

> "EB" == Eric Blake <[EMAIL PROTECTED]> writes: EB> According to [EMAIL PROTECTED] on 10/13/2007 6:57 PM: >> fold (GNU coreutils) 5.97 EB> Consider upgrading. The latest stable coreutils is at 6.9. I'll tell Debian to upgrade. >> * counts bytes, not columns, even without -b >> * has no co

tail -n N

man tail -c, --bytes=N output the last N bytes -n, --lines=N output the last N lines, instead of the last 10 say -c N, --bytes=N etc. just like grep(1). P.S., For compatibility `tail' also supports an obsolete usage `tail -COUNT[bcl][f] [FILE

664 vs. touch -d now

Gentlemen, what's the deal, or have we been through this before and I'm just not using the current version or something here on Debian sid GNU/Linux 2.6.22. $ ls -al drwxr-xr-x 2 jidanni jidanni 60 2008-01-03 08:40 . drwxr-xr-x 3 jidanni jidanni 60 2008-01-03 08:23 .. -rw-rw-r-- 1 root

Re: 664 vs. touch -d now

Thanks for fixing it, as I don't want to get that deep... OK, Over and out. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

  1   2   >