Bet you don't document anywhere that/why
$ echo a|cat - -
will only give one a.
Or maybe even raise an error...
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
[EMAIL PROTECTED] wrote:
Bet you don't document anywhere that/why
$ echo a|cat - -
will only give one a.
Or maybe even raise an error...
Seems obvious to me.
Perhaps the following is more obvious :)
$ echo mouse | cat - -
Pádraig.
___
On Monday 14 January 2008, [EMAIL PROTECTED] wrote:
Bet you don't document anywhere that/why
$ echo a|cat - -
will only give one a.
what were you expecting to happen ? it is not possible for cat to re-read
stdin once it has consumed it.
-mike
signature.asc
Description: This is a digitally
MF what were you expecting to happen ? it is not possible for cat to
MF re-read stdin once it has consumed it.
Yes, but you don't document it I bet. At least not in the path that
starts with man cat.
Just reading the coreutils docs, one wouldn't know why
$ date|cat q b - c q - q - b
worked
On Tuesday 15 January 2008, [EMAIL PROTECTED] wrote:
what were you expecting to happen ? it is not possible for cat to
re-read stdin once it has consumed it.
Yes, but you don't document it I bet. At least not in the path that
starts with man cat.
Just reading the coreutils docs, one
Yes yes. I'm just saying supposing a theoretical new user's first
encounter with all this stuff was the document trail that started with
the cat man page, then he would think - was broken.
So still an understanding of Unix is implied as the docs perhaps
describe 95% but not yet 100% of what one
On Jan 16, 2008 12:01 AM, [EMAIL PROTECTED] wrote:
Yes yes. I'm just saying supposing a theoretical new user's first
encounter with all this stuff was the document trail that started with
the cat man page, then he would think - was broken.
The best place to document this could well be a
J But the main problem is to figure out where to put such a document
J so that new users will actually read it. What do you think?
Somewhere around
$ info -o - coreutils|grep -C 2 Intro
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
-p does not use the mode from -m for parent directories:
# mkdir -p -m 700 foo/bar
# ls -ld foo foo/bar
The directory foo does not have the correct permissions.
I can imagine:
# mkdir -p -m 500 foo/bar
Causing problems though, but unless it's easy to handle, I would ignore
it (the user got
To whom it may concern:
I believe I have identified a bug in the GNU coreutils date
utility when handling the PDT timezone.
I'm running Fedora 8 kernel 2.6.23.9-85.fc8, and the command date -
-version reports: date (GNU coreutils) 6.9
When using the -d option to display the specified time (vs
On Tue, 15 Jan 2008, [EMAIL PROTECTED] wrote:
I believe I have identified a bug in the GNU coreutils date utility
when handling the PDT timezone.
I'm running Fedora 8 kernel 2.6.23.9-85.fc8, and the command date -
-version reports: date (GNU coreutils) 6.9
[snip]
$ date -dTue Jan 14
Philip Rowlands [EMAIL PROTECTED] writes:
Although the coreutils documentation cautions about using ambiguous
timezone labels like this,
The actual problem is the reverse of the original complaint.
Coreutils should reject a usage like 'date -d Tue Jan 14 08:25:26 EDT
2008 +%s', because that
12 matches
Mail list logo
