[comp.mail.mush] possible Bug in set-command

pk@unidoct.chemietechnik.uni-dortmund.de (Peter Koch) (05/30/90)

I installed mush 7.1.1 and encountered a strange behaviour of the
'set'-command.

If You try to 'set' a variable to a value with less than three letters, You
catch an 'Unmatched ".'

Example:

set prompt=">"
Unmatched ".
set prompt="> "
Unmatched ".
set prompt=">  "
(now 'prompt' is set correctly)

It's the same if You use ' instead of ".

For this reason the distributed files Mushrc and Mail.rc produce lots of
'Unmatched ..' messages

I'm no .mushexpert :-), so could some of those please help me.

  Thanx and bye
-- 
Peter Koch                     EUnet:  pk@unidoct.chemietechnik.uni-dortmund.de
Fachbereich Chemietechnik
Universitaet Dortmund
4600 Dortmund 50               Tel.:   +49 231 755 2633

schaefer@ogicse.ogi.edu (Barton E. Schaefer) (06/02/90)

In article <579@unidoct.chemietechnik.uni-dortmund.de> pk@unidoct.chemietechnik.uni-dortmund.de (Peter Koch) writes:
} I installed mush 7.1.1 and encountered a strange behaviour of the
} 'set'-command.
} 
} If You try to 'set' a variable to a value with less than three letters, You
} catch an 'Unmatched ".'
} 
} Example:
} 
} set prompt=">"
} Unmatched ".
} set prompt="> "
} Unmatched ".
} set prompt=">  "
} (now 'prompt' is set correctly)

The "set" command itself does not do any parsing of quotation marks.  That
message comes only from the input parser, before any command is called.

I've already sent mail to Peter, but if anyone else is seeing this sort
of problem please try (from within "script" or some similar program to
capture the output):

    debug 4
    set prompt=">"

then send me the results.  Thanks.
-- 
Bart Schaefer						schaefer@cse.ogi.edu