Adrian Aichner <adrian(a)xemacs.org> wrote:
From: Greg Green <gregory.p.green(a)boeing.com>
Subject: undefined function in tempo.el
[snip]
I have recently switched from emacs to xemacs. My customization for
python-mode
uses tempo.el to insert code in new buffers. It doesn't work anymore. I get the
'symbol is void: deactivate-mark'
[snip]
I've answered this one before. It was Mandrake's fault in at least one
case. See (I hope these links work!):
<
URL:http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=L...
<
URL:http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=p...
<
URL:http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=p...
Greg, can you determine where the binding of transient-mark-mode comes
from? Is it in your personal .emacs, or in the system-wide
initialization files? If the latter, who wrote it?
Tempo has not been updated for a long time. Should we maybe just change
the test in the XEmacs version so that it looks at running-xemacs
instead of transient-mark-mode?
--
Jerry James
http://www.ittc.ku.edu/~james/