In your mail: >From: Rainer Koehler <[EMAIL PROTECTED]> >Reply-To: >To: [EMAIL PROTECTED] >Subject: Re: FVWM: Re: [HELP]PipeRead Strange Error Message > > Doesn't this look like a line of ps-output to you? ;-) >
That's why I found it weird. > When you grep for something in ps-output, you usually also pick up the > process of the grep itself (since it's argument is exactly what it's > looking for). In this case, it picks up the sh-process created by > fvwm. > > I know two ways to get around that: > - grep for a regexp like '[F]vwm' (because it doesn't match itself) > - or add a 'grep -v grep' to the command line > Thank you! `grep -v grep' solved the problem! Now I know the best way to test out PipeRead command stream is: % exec COMMAND > BTW, I would follow Mikhael's advice and put all that into a separate > shell-script. Life is much easier if reduce the number of quotes, > backslashes etc. And a script is much easier to debug because you can > just call it from a shell-prompt. > I agree. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
