Programming

I am using csh.

Output of command jobs
[RTL]{145}>jobs
[1] + Running /home/alokg/nedit-5.5-Linux-x86/nedit .cshrc
[2] Running /home/alokg/nedit-5.5-Linux-x86/nedit build/irun_usb2.log
[3] Running /home/alokg/nedit-5.5-Linux-x86/nedit ...

But if we do

jobs| grep R

we get nothing.

It seems grep is unable to get any stream out of jobs

I had tried
jobs > a
which effects in redirecting the output of jobs to file a . Hence jobs is not directing output to STDERR in case of csh.

Hi.

On the system I use, the bash builtin jobs writes to STDERR, so one would need (using your example):

Code:

jobs 2>&1 | grep R

See man bash for details.

Best wishes ... cheers, drl

Thanks for the reply

I forget to mention that I am using csh.
In csh it seems that output of jobs is directed to STDOUT not STDERR
as
jobs > a is redirecting the outputs to file a
I donot need to do jobs >& a as needed for redirect STDERR

Hence, I am finding the behavior as starange

csh is strange and I have no idea why anyone uses it.

You are wrong. jobs writes to standard error, and I'm not sure it's possible to direct standard error to standard output except for the purpose of writing to a file.

It's easy to see it's writing to standard error, as grep which reads from standard output, gets nothing to read:

Code:

[scott:~/scripts] % sleep 100 &
[1] 37754
[scott:~/scripts] % jobs
[1]  + Running                       sleep 100
[scott:~/scripts] % jobs | grep sleep
[scott:~/scripts] %