[7063] in SIPB bug reports
Re: walk-in bug with exmh
daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Wed Dec 2 09:04:51 1998
Date: Wed, 2 Dec 1998 09:04:42 -0500 (EST)
From: Jacob Morzinski <jmorzins@MIT.EDU>
To: Matthew Belmonte <belmonte@MIT.EDU>
Cc: bug-sipb@MIT.EDU
In-Reply-To: <199812020216.VAA11487@belmonte.ne.mediaone.net>
On Tue, 1 Dec 1998, Matthew Belmonte wrote:
> A user came in with the following problem, which golem says is a bug in exmh's
> Tcl code. In this instance of the bug, the string "So what?" seems to have
> been incorrectly quoted. (I am not Tcl-clueful.)
Did the user leave a username? While I'm not at a terminal where
I can easily test right now, my initial suspicion is that the
problem is caused custom modifications the user made to their
exmh code.
> When the user hits the "Compose" button, the following message (truncated here)
> appears:
>
> invalid command name ".seditSo"
> while executing
> ".seditSo What?/9.but.send cget -command"
> ("uplevel" body line 1)
It would be useful to see a full backtrace. Without it, all I
can say is:
% cd /mit/sipb/share/exmh-2.0.2
% grep '.but.send cget -command' *.tcl
Exit 1
%
The "So What?" embedded in the middle of tcl code seems bizarre
to me. AFS cache corruption?
> Nuking .exmh* changes nothing.
That's a good start. There's also a possibility that a
~/.tk/exmh directory contains user-level customizations that
rewrite parts of exmh's code.
Jacob Morzinski jmorzins@mit.edu
