From owner-freebsd-bugs@FreeBSD.ORG Sat Oct 2 03:00:42 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F4E116A4CE for ; Sat, 2 Oct 2004 03:00:42 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 808B243D3F for ; Sat, 2 Oct 2004 03:00:42 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i9230ghw053790 for ; Sat, 2 Oct 2004 03:00:42 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9230gC5053789; Sat, 2 Oct 2004 03:00:42 GMT (envelope-from gnats) Date: Sat, 2 Oct 2004 03:00:42 GMT Message-Id: <200410020300.i9230gC5053789@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Subject: Re: bin/34811: sh: "jobs" is not pipeable X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kerochan2@gmail.com List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2004 03:00:42 -0000 The following reply was made to PR bin/34811; it has been noted by GNATS. From: To: Cc: Subject: Re: bin/34811: sh: "jobs" is not pipeable Date: Sat, 2 Oct 2004 02:53:31 +0000 (GMT) The standard behaviour is this: faber $ (sleep 10 & jobs | cat) [1]+ Running sleep 10 & faber $ (sleep 10 & jobs | grep '.') [1]+ Running sleep 10 & Commands inside () are forced into a subshell; sleep 10 is then started in the background; jobs is a shell builtin, but it's output must still be pipable; AND IT IS! Does the sequence "(sleep 10 & jobs | cat)" produce output at you? [It should.]