Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!veritas!amdcad!sun!exodus!argv
From: argv@turnpike.Eng.Sun.COM (Dan Heller)
Newsgroups: comp.mail.mush
Subject: Re: 7.2.0 - can't please everyone
Message-ID: <2869@exodus.Eng.Sun.COM>
Date: 15 Nov 90 19:02:18 GMT
References: <741@parcplace.com> <2447@exodus.Eng.Sun.COM> <1150@happy.osc.edu>
Sender: news@exodus.Eng.Sun.COM
Distribution: comp
Organization: O'Reilly && Associates
Lines: 25

In article <1150@happy.osc.edu> phil@cgrg.ohio-state.edu (Phil Ritzenthaler) writes:
>  . . it used to be that after
> reading a message and going back to the prompt, vrom the prompt you could hit 
> the return key and the next message would be displayed  (like mail does).  Now,
> when I hit return, the only thing I get is my prompt.  I don't want another
> prompt.  I want the NEXT MESSAGE!

Check the value of your $newline variable.  If it's set, then hitting
the newline will cause the command it's set to to be executed.  If it's
set, but not to a value, then nothing will happen:

set newline     #nothing happens, get your prompt back
set newline=dt  #newline does a "delete; next" command
unset newline   #default behavior -- print the next message

Now, why *your* particular newline variable got changed is beyond me.
It may be that whoever installed the new version of Mush on your machine
also installed a default Mushrc that was different from what you were
used to.

--
dan
----------------------------------------------------
O'Reilly && Associates   argv@sun.com / argv@ora.com
Opinions expressed reflect those of the author only.