🚀 go-pugleaf

a) a .bashrc that contains

   if [ "$PS1" != "" && $SHLVL -gt 1 ]
   then
	   echo bah
   fi

   will cause bash to dump core; said code appears to produce an error message
   (cryptic as it may be) as it should when the shell is run interactively

b) [ error messages for csh operators used by mistake should be fixed;
   with the large population of tcsh users you can expect to see migrating,
   this will count as a large class of errors while people rewire their
   brains.  I'd really like to see "==": illegal operator, "&&": dumping
   core, and other informative messages.

c) Can the &#^*%&! insertion of a * at the beginning of the prompt when
   a line is edited be turned off?  it appears as well that only the
   prompt is shifted as well, which is disconcerting if not wrong.

d) there should be a wholesale way to get emacs behaviour for cut and
   paste (NUL sets mark, ^W cuts, ^Y pastes).  Few users I know that use
   emacs regularly rely on the pre-tcsh behaviour.

Jean-Francois Lamy               lamy@ai.utoronto.ca, uunet!ai.utoronto.ca!lamy
AI Group, Department of Computer Science, University of Toronto, Canada M5S 1A4