Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!tut.cis.ohio-state.edu!cica!iuvax!rutgers!att!cbnewsm!ste
From: ste@cbnewsm.ATT.COM (Shaun T. Erickson)
Newsgroups: comp.mail.mush
Subject: Why is this (partially) broken now?
Keywords: toolplaces, arguments, order
Message-ID: <3002@cbnewsm.ATT.COM>
Date: 20 Aug 89 17:37:53 GMT
Reply-To: ste%hudson@aloft.ATT.COM (Shaun T. Erickson)
Organization: AT&T Bell Labs, Allentown, PA
Lines: 23

When I execute the "toolplaces" command, after setting up my sunview
screen to my tastes, the line for mush reads as:

mush       -Wp   88  47 -Ws 703 761 -WP  584 588 -Wi -Wb   0   0 140 -Wf 255 130   0 -t -Wg

This always worked in my setup file just fine, before I switched to the
mushview version. Now mush blows up on this - complaining about invalid
arguments - resulting in mush coming up in line mode, in compose mode,
and asking for a subject for the letter which is addressed to all the
command line arguments (except for the first argument, which it choked on).

I have found that if I move the single mushview argument, the "-t", to be
the first argument to mush, it works just fine, but this means I now have
to manually edit my startup file - not very freindly, eh?

Why is this broken now, and which should be fixed: mush, toolplaces, or me?

 8-{)> 
-- 
 ------------------------------------------------------------------------------
 Shaun T. Erickson       Contracted to AT&T Bell Labs, Allentown, Pennsylvania
 Internet: ste%hudson@aloft.att.com             UUCP: ...!att!aloft!hudson!ste
 Standard Disclaimer.                                     This space for rent.