I am using the win32 version of xemacs 21.4 in this case. I also use Linux
and SGI but haven't yet tried it there.
Just tried xemacs 21.1 on sgi, and I can't even get python-mode to work. It
just locks up. I think I'll start a new init.el file and add my stuff
gradually until I find the problem.
I know that I didn't change the binding to transient-mark-mode.
Thanks for the help. I'll post again if I discover something more useful.
-----Original Message-----
From: Jerry James [mailto:jamesï¼ xemacs.org]
Sent: Thursday, July 11, 2002 1:39 PM
To: Adrian Aichner
Cc: XEmacs Beta List; Green, Gregory P
Subject: Re: [comp.emacs.xemacs] undefined function in tempo.el
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...
.15019%40read2.inet.fi>
<
URL:http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=p...
40diannao.ittc.ukans.edu>
<
URL:http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=p...
40diannao.ittc.ukans.edu>
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/