Re: The /r error message while running a script?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Kevin Markle on 3/27/2007 2:29 PM:
> touch: cannot touch
`/cygdrive/e/wsus/wsus_update_report.outr': No such
> file or directory
> ./patch.sh: line 11: $'r': command not found

I like this new look, if I must say so myself!  No more
overwriting the
line and starting the error message with just a :. 
Hopefully it clues
more people in to the real problem with less frustration now
that the r
shows up in the error message.

But still, I can't help wonder if this email exchange was
worth a *sip* or
not.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at
home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFGCbqW84KuGfSFAYARAg0RAJ0U95NxcVax/wnxTe0SStA49Yo2EQCg
mz3W
n0EKiLKQ1dd66UKYBzIyK0I=
=AcY7
-----END PGP SIGNATURE-----

On Tue, Mar 27, 2007 at 06:45:10PM -0600, Eric Blake wrote:
>According to Kevin Markle on 3/27/2007 2:29 PM:
>> touch: cannot touch
`/cygdrive/e/wsus/wsus_update_report.outr': No such
>> file or directory
>> ./patch.sh: line 11: $'r': command not found
>
>I like this new look, if I must say so myself!  No more
overwriting the
>line and starting the error message with just a :. 
Hopefully it clues
>more people in to the real problem with less frustration
now that the r
>shows up in the error message.
>
>But still, I can't help wonder if this email exchange
was worth a *sip* or
>not.
r
If you have to ask, I'd say it's best to err on the side of
sipping.r
r
cgfr