Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!malgudi!sunc.osc.edu!phil
From: phil@osc.edu (Phil Ritzenthaler)
Newsgroups: comp.mail.mush
Subject: Re: 7.2.0 - can't please everyone
Message-ID: <1155@happy.osc.edu>
Date: 16 Nov 90 15:14:30 GMT
References: <2869@exodus.Eng.Sun.COM>
Distribution: comp
Organization: Advanced Computing Center for Arts & Design
Lines: 34

From article <2869@exodus.Eng.Sun.COM>, by argv@turnpike.Eng.Sun.COM (Dan Heller):
> 
> 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.
> 

I'm the culprit when it comes to installing anything.  The only thing I had
changed in the MUSHRC from Mail User's Shell (7.1.2 7/11/90) was I unset hold
that is defined in the Mail.rc files.

That's what I get for not reading the *&^^(*^% default files.  Commenting out 
the line (and READING the &*^%@# Mushrc file) I found:
	# Hitting <CR> should do nothing (helps make mush more shell-like).  If
	# newline is not set, hitting <CR> prints the next message (like Mail).
	# This variable could be set to any mush command.
	#set newline

Thank you for you help!

-- 
Phil Ritzenthaler  The Advanced Computing Center for the Arts & Design (ACCAD)
Systems Manager    The Ohio State University
                   UUCP: ...!{pyramid,killer}!grumpy.cgrg.ohio-state.edu!phil
(614) 292-3416     ARPA: phil@grumpy.cgrg.ohio-state.edu