🚀 go-pugleaf

1) If you have a path line like
	PATH=:/bin:/usr/bin:~/bin:/usr/local/bin

   then when it is exported, the ~ is not expanded.  This confuses
   subsequent invocations of /bin/sh or other programs that parse
   paths, for example make.  Csh does expand components of the path it
   exports.

2) the present simple-minded history substitution has some surprises
   for csh users.  I have noted in the past the lack of delimiter
   escaping or :gs global substitutions or "&" pattern replacement.
   This one annoys me a lot: you can't add slashes with ^.^./^ as this
   is treated as "!!:s/././/" which does nothing at all.  Nor does
   ^x^xx^lly (or the equivalent ":s/x/xx/lly") do what is expected
   (i.e. turn txt into txxtlly).  Some serious rewrite of the history
   editing code would need to be done to make bash csh-compatible in
   this area.  Is this a desired end, or is there some other model of
   history editing bash is trying to emulate?  I have started looking
   at these problems and may eventually produce a better history
   editor.

Greg.

BTW: I have patches to add FIGNORE to the 1.03 filename completion (a
la SunOS csh set fignore ()) if anyone is interested.