Hi Brian,
On 2015-04-14 05:12, brian m. carlson wrote:
On Mon, Apr 13, 2015 at 11:48:50PM +1000, Luke Mewburn wrote:
I appreciated the opportunity to learn about tcgetpgrp(3). The Windows
folks will probably need to stub that function out, but they're no worse
off than they were before.
On Mon, Apr 13, 2015 at 11:01:04AM -0400, Nicolas Pitre wrote:
| That's what happens; the suppression only occurs if the process is
| currently background. If I start a long-running operation (such as git
| fsck), the progress is displayed. I then suspend background, and the
|
On Mon, Apr 13, 2015 at 11:48:50PM +1000, Luke Mewburn wrote:
Hi,
I've noticed that when a long-running git operation that generates
progress output is suspended and converted to a background process,
the terminal still gets spammed with progress updates (to stderr).
I've explicitly
On Mon, Apr 13, 2015 at 10:11:09AM -0400, Nicolas Pitre wrote:
| What if you suspend the task and push it into the background? Would be
| nice to inhibit progress display in that case, and resume it if the task
| returns to the foreground.
That's what happens; the suppression only occurs
On Mon, 13 Apr 2015, Luke Mewburn wrote:
Hi,
I've noticed that when a long-running git operation that generates
progress output is suspended and converted to a background process,
the terminal still gets spammed with progress updates (to stderr).
Many years ago I fixed a similar issue in
Hi,
I've noticed that when a long-running git operation that generates
progress output is suspended and converted to a background process,
the terminal still gets spammed with progress updates (to stderr).
Many years ago I fixed a similar issue in the NetBSD ftp progress
bar code (which I
On Tue, 14 Apr 2015, Luke Mewburn wrote:
On Mon, Apr 13, 2015 at 10:11:09AM -0400, Nicolas Pitre wrote:
| What if you suspend the task and push it into the background? Would be
| nice to inhibit progress display in that case, and resume it if the task
| returns to the foreground.
7 matches
Mail list logo