Hi,
It seems to me that EMPTY field printing in join is borked, or I am misguided.
Here is a minimal example:
join -e EMPTY -o 1.1 1.2 2.2 /tmp/a /dev/null
/tmp/a being single line: b 2
I think that the output should be b 2 EMPTY not none like it is with
included in coreutils 6.9.
Best
Slawek Zak [EMAIL PROTECTED] wrote:
It seems to me that EMPTY field printing in join is borked, or I am misguided.
Here is a minimal example:
join -e EMPTY -o 1.1 1.2 2.2 /tmp/a /dev/null
/tmp/a being single line: b 2
I think that the output should be b 2 EMPTY not none like it is with
John Cowan [EMAIL PROTECTED] writes:
Well and good, but it seems to me that writing an explicit 0 actually
does make an explicit request.
This topic came up when I first added that feature, and originally I
agreed with you, but others did not and their arguments were
persuasive. The
I forgot to include a NEWS item for the May 2 change on size suffixes.
Sorry about that. Here it is:
2007-05-14 Paul Eggert [EMAIL PROTECTED]
* NEWS: Mention the suffix change installed on 2007-05-02.
diff --git a/NEWS b/NEWS
index ea3aafb..ed3ab49 100644
--- a/NEWS
+++ b/NEWS
@@
Jan Engelhardt [EMAIL PROTECTED] writes:
Then the manpgea is broken instead:;
Thanks for mentioning that. Here is a patch to the man page.
2007-05-14 Paul Eggert [EMAIL PROTECTED]
* man/chmod.x: Document chmod's behavior with setuid and setgid bits.
Remove misleading
(Apologies to those, if any, who got an earlier version of this message.)
Paul Eggert scripsit:
The counterargument is that it's strange if a leading
zero changes the semantics of a number, as this is not what many
people expect.
Fair enough. However, if the directory has mode 6755 and you
Paul Eggert [EMAIL PROTECTED] wrote:
Thanks for mentioning that. Here is a patch to the man page.
2007-05-14 Paul Eggert [EMAIL PROTECTED]
* man/chmod.x: Document chmod's behavior with setuid and setgid bits.
Remove misleading implication about leading zero. Problem
