No need to.  The problem is fixed in a later version
(csh-5.2.6-6.i386.rpm) of the same package.

With that installed instead of csh-5.2.6-2.i386.rpm, I now get:

   $ csh -x
   [jww@olorin]$ grep '^asd' xxx1 xxx2
   grep ^asd xxx1 xxx2
   xxx1:asdf
   [jww@olorin]$ grep '^asd' xxx*
   grep ^asd xxx1 xxx2
   xxx1:asdf

Ask the administrator of bolt to upgrade or to replace /bin/csh with a
link to tcsh (uninstalling csh-5.2.6-2 seems to do that)--or switch to
tcsh yourself.

--
John Wingate                                       wing...@worldpath.net

Is there an explanation of what caused the problem in the first place?  I
still don't see how it can happen, unless csh is spontaneously inserting
backslashes into the parameter, i.e. it's rewriting

grep '^foo' j*

to:

grep '\^foo' j*

--
Barry Margolin, bar...@bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

It's actually rewriting it to:

   grep \^\f\o\o junk1 junk2

See an earlier post of mine in this thread
(<tLUc4.48180$xC4.477...@newshog.newsread.com>) for an example using
"csh -x" to show the rewriting.

--
John Wingate                                       wing...@worldpath.net

tcsh may not be 100% csh compatible - I'm not sure - but if it isn't,
you must be using some pretty arcane csh features, which probably isn't
a good idea anyway :)  tcsh is much better for interactive use: it has
wonderful command completion functionality.  I avoid /bin/csh where
possible (and my scripts are in /bin/sh.)

--
Reinier Post