From:
[email protected]
It looks as if it'll be a while before a tk8.4-compliant version of
exmh is packaged by the maintainer. The last activity on this bug is
more than a year old and there has been no such update.
Until then, bugs like #176642 can be fixed with the following patch,
which is based on one I found at
http://mercea.net/~exmh/html/exmh-users/2002-12/msg00058.html in case
you're curious:
--- exmh.dist 2004-08-16 16:30:34.000000000 -0500
+++ exmh 2004-08-16 16:30:09.000000000 -0500
@@ -29,6 +29,17 @@
# appear all alone.
wm withdraw .
+if {[info commands "tkEntrySeeInsert"] == ""} {
+ # Dang - the procs have been renamed - restore them
+ tk::unsupported::ExposePrivateCommand tkEntrySeeInsert
+ tk::unsupported::ExposePrivateCommand tkEntryBackspace
+ tk::unsupported::ExposePrivateCommand tkMenuUnpost
+ tk::unsupported::ExposePrivateCommand tkTextResetAnchor
+ tk::unsupported::ExposePrivateCommand tkEntryButton1
+ tk::unsupported::ExposePrivateCommand tkTextButton1
+ tk::unsupported::ExposePrivateVariable tkPriv
+}
+
proc auto_path_update { path } {
# Add library directories to the auto_path,
# ensuring that later paths have precedence
This re-exposes a lot of commands and one variable which are made
private in tk8.4.
It would be better to package the newer version of exmh, but if that's
not possible to do in a timely man