From: "Matt Wozniski" <godlygeek@gmail.com>
To: zsh-users@sunsite.dk
Subject: Fwd: jobs -d &>/dev/null still produces output?
Date: Fri, 3 Nov 2006 14:11:22 -0500 [thread overview]
Message-ID: <17393e3e0611031111s30f1c042g205e864ffeb41c16@mail.gmail.com> (raw)
In-Reply-To: <17393e3e0611031107w6e44a205tb278a667a9882a8c@mail.gmail.com>
Crap, I sent this to Michael instead of the group accidentally...
Sorry Michael!
'1>' or just '>' redirects STDOUT, '2>' redirects STDERR, and '&>'
redirects both. My test case should redirect both. Try getting rid of the
'2' in your example and it will still give the behavior that you
described. jobs is doing something special, and the source code just
confused me more. :)
~Matt
On 11/3/06, Michael Hernandez <sequethin@gmail.com> wrote:
>
> On Nov 3, 2006, at 1:48 PM, Matt Wozniski wrote:
>
> > I'm a bit confused by something zsh is doing.
> >
> > Test case:
> >
> > sleep 1000 &
> > jobs -d &>/dev/null
> >
> > Why does this still produce output? Is there any way to redirect the
> > line that's still appearing on screen? And what on earth is the
> > 'shout' file descriptor tied to? :)
> >
> > Thanks!
> >
> > ~Matt
>
> Could be that jobs is using STERR not just STDOUT
>
> Try redirecting STDERR, for example
>
> lskdjf 2&>/dev/null
>
> Produces no output (it should say "command not found" or something
> similar)
>
> --
> Mike
>
next prev parent reply other threads:[~2006-11-03 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 18:48 Matt Wozniski
2006-11-03 19:02 ` Michael Hernandez
[not found] ` <17393e3e0611031107w6e44a205tb278a667a9882a8c@mail.gmail.com>
2006-11-03 19:11 ` Matt Wozniski [this message]
2006-11-03 19:42 ` Peter Stephenson
2006-11-03 19:59 ` Matt Wozniski
2006-11-04 11:51 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17393e3e0611031111s30f1c042g205e864ffeb41c16@mail.gmail.com \
--to=godlygeek@gmail.com \
--cc=mjw@drexel.edu \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).