Re: Emacspeak 11.0 on xemacs 21.2.27

Martin -- 1) Yes, I think it would be a good idea to separate the lossage and messages buffers and provide a keystrok for popping up the messages buffer. 2) The xemacs compiler appears to complain incorrectly sometimes about special variables --this is with (require 'cl) and (declare (special ...)) inside function bodies. It also appears to have problems the cl (declaim ...) construct --it continues to produce the warning that that declaration is supposed to suppress. --need to create a minimal .el file that demonstrates this. 3) I guess inhibit-point-motion-hooks got dropped in xemacs. Not that I care --emacspeak doesn't use this -however in the case of FSF emacs emacspeak carefully sets this variable at specific times in order to avoid emacs doing unexpected things. I've worked around it for now by introducing an inline function that I call rather than directly referring to variable inhibit-point-motion-hooks --is there more standard fsf-compat way of doing this? 4) Bill (wmperry)-- emacspeak-w3 throws a strange warning when loaded --the error is being thrown by the bytecompiler saying invalid bytecode --this is after comiling all emacspeak files with xemacs. --the problem appears to be in the section of the code where we insert the emacspeak help into the widgets via symbol emacspeak-help -- Best Regards, --raman Email: raman(a)cs.cornell.edu WWW: http://cs.cornell.edu/home/raman/ PGP: http://cs.cornell.edu/home/raman/raman.asc