Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!CSE.OGI.EDU!schaefer
From: schaefer@CSE.OGI.EDU (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: mush 'cmd' use
Message-ID: <9007312150.AA06354@cse.ogi.edu>
Date: 31 Jul 90 21:50:49 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 44

On Jul 31,  1:16pm, Tony Kanakis wrote:
} Subject: mush 'cmd' use
}
} _____________________________________________________________________________
} cmd two 'set print_cmd="enscript -b'TO:  CUST. SUP.'-fCourier10 -Plaser2; lpq -Plaser2"'
} _____________________________________________________________________________
} 
} 	I would type in 'two' while in mush and then 'lpr' and nothing would 
} print out.  Can anyone explain this?

It might have something to do with the four single quotes I see in that
particular line.  When in doubt, check your quote marks!  Unbalanced or
incorrectly nested quotes are the most common reason I've seen for cmds
not working (both my own and ones that other people send me :-).

The parse of that line is (newlines between words):

    cmd
    two
    'set print_cmd="enscript -b'TO:
    CUST.
    SUP.'-fCourier10 -Plaser2; lpq -Plaser2"'

which installs the cmd as

  set print_cmd="enscript -bTO: CUST. SUP.-fCourier10 -Plaser2; lpq -Plaser2"

which will call enscript as

    enscript
    -bTO:
    CUST.
    SUP.-fCourier10
    -Plaser2

In summary, I think you want slightly different quoting and a space
before the -f (backslashed-newlines for readability):

    cmd two \
    'set print_cmd="enscript -b'"'TO:  CUST. SUP.'"' -fCourier10 -Plaser2;\
    lpq -Plaser2"'

-- 
Bart Schaefer						schaefer@cse.ogi.edu