I think 3 years for anyone to issue any sort of response to the 3 people
that mention they are affected by this change in behavior of default
installed tools says a lot about how much Ubuntu cares about the issue,
so it quite obvious that it doesn't matter what their users think
anymore. it's a sa
Nothing in the preceding comments supports the notion that this is a
"regression bug".
(no point in arguing if you didn't understand the technical explanation - bye)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
the very definition of a regression bugs is when an upgrade changes a
behavior in a such way that a function no longer works the same way.
this is a regression bug. Plain as day. "-W interactive" is an
unintuitive solution, and it's not exactly clear what's going on even in
12.10's man page.
and
It's not a bug, but as they say a feature: gawk tests if stdout is a tty at
startup. If so, all writes are flushed.
This produces the effect which you see. However, it makes gawk slower than it
might be.
mawk has an option -W interactive which makes stdout unbuffered (with the
corresponding
This has been untouched for seven months and through one release. I
just spent an hour (I don't really have) trying to figure out why my
pipe to awk wasn't working properly. This bug is easily resolvable by
just making gawk the default awk again.
--
tail piped to awk not processing
https://bugs
Thank you for sending in this bug report! I also see this behaviour on
Ubuntu 9.04 amd64 architechure. I even tried cat'ing messages, which
worked, but tailing them (-f or not) didn't work. Odd.
** Changed in: mawk (Ubuntu)
Status: New => Confirmed
--
tail piped to awk not processing
h
