Article View: comp.mail.mush
Article #386Re: possible Bug in set-command (7.1.1)
From: Barton E. Schaefer
Date: Fri, 01 Jun 1990 17:59
Date: Fri, 01 Jun 1990 17:59
29 lines
1359 bytes
1359 bytes
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
Technical Details
Message-ID:
<9671@ogicse.ogi.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!schaeferReferences:
<579@unidoct.chemietechnik.uni-dortmund.de>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!schaefer From: schaefer@ogicse.ogi.edu (Barton E. Schaefer) Newsgroups: comp.mail.mush Subject: Re: possible Bug in set-command (7.1.1) Keywords: bug, set Message-ID: <9671@ogicse.ogi.edu> Date: 1 Jun 90 17:59:05 GMT References: <579@unidoct.chemietechnik.uni-dortmund.de> Distribution: comp Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR Lines: 29