lamy@ai.utoronto.ca (Jean-Francois Lamy) (08/03/89)
In private mail, Tom Quinn (trq@radio.astro.utoronto.ca) points out that if you happen to rcp while you have mail, bash's spurious output will confuse rcp. This would explain both why the problem is intermittent and why it was observed on several machines/OS combinations. Until it is fixed for good, a work-around is to fix your config files to unset MAILCHECK if test -t fails. Jean-Francois Lamy lamy@ai.utoronto.ca, uunet!ai.utoronto.ca!lamy AI Group, Department of Computer Science, University of Toronto, Canada M5S 1A4
bfox@aurel.caltech.edu (Brian Fox) (08/04/89)
Date: 3 Aug 89 14:18:04 GMT From: lamy@neat.cs.toronto.edu (Jean-Francois Lamy) Sender: bug-bash-request@prep.ai.mit.edu In private mail, Tom Quinn (trq@radio.astro.utoronto.ca) points out that if you happen to rcp while you have mail, bash's spurious output will confuse rcp. This would explain both why the problem is intermittent and why it was observed on several machines/OS combinations. Uh, I don't have this problem. Perhaps the bug is gone now? We can try a sample test. I send myself mail, and then (when I know it is in the mailbox) I type bash -c "echo foo" The only thing that I get is "foo". If you get a message about mail, then that would explain the problem. Brian
bet@ORION.MC.DUKE.EDU (Bennett Todd) (08/04/89)
I send myself mail, and then (when I know it is in the mailbox) I type bash -c "echo foo" The only thing that I get is "foo". If you get a message about mail, then that would explain the problem. I get the message about mail unless I have that incantation if test "$PS1" = "";then unset MAILCHECK fi in my .bashrc. -Bennett bet@orion.mc.duke.edu
bfox@AUREL.CALTECH.EDU (Brian Fox) (08/04/89)
Date: Thu, 3 Aug 89 19:35:41 EST
From: ray@gibbs.physics.purdue.edu (Ray Moody)
Bash -c "echo foo" tells me that I have new mail.
I don't know why yet. It seems that something, somewhere, is
setting prompt_printable.
Don't worry about this problem, it is fixed in 1.03.
Brian