[ESS] Xemacs+ESS problem under Windows
John Fox
jfox at mcmaster.ca
Thu Oct 28 16:24:41 CEST 2004
Dear Stephen,
Here's the backtrace:
Signaling: (invalid-read-syntax "Cannot read unreadable object")
eval-buffer()
ess-sqpe-versions-create()
(setq ess-sqpe-versions-created (ess-sqpe-versions-create))
(progn (setq ess-sqpe-versions-created (ess-sqpe-versions-create)) (setq
ess-rterm-versions (ess-find-rterm)) (setq ess-rterm-versions-created
(ess-rterm-versions-create)))
(if ess-microsoft-p (progn (setq ess-sqpe-versions-created ...) (setq
ess-rterm-versions ...) (setq ess-rterm-versions-created ...)) (setq
ess-r-versions-created (ess-r-versions-create)))
(let ((ess-sqpe-versions-created) (ess-rterm-versions-created)
(ess-r-versions-created) (ess-versions-created)) (if ess-microsoft-p (progn
... ... ...) (setq ess-r-versions-created ...)) (setq ess-versions-created
(ess-flatten-list ...)) (when ess-versions-created (let ... ...)))
load-internal("ess-site" nil t nil undecided)
load("ess-site" nil t nil)
require(ess-site)
eval((require (quote ess-site)))
eval-interactive((require (quote ess-site)))
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
Regards,
John
--------------------------------
John Fox
Department of Sociology
McMaster University
Hamilton, Ontario
Canada L8S 4M4
905-525-9140x23604
http://socserv.mcmaster.ca/jfox
--------------------------------
> -----Original Message-----
> From: Stephen Eglen [mailto:S.J.Eglen at damtp.cam.ac.uk]
> Sent: Thursday, October 28, 2004 9:18 AM
> To: John Fox
> Cc: ess-help at stat.math.ethz.ch
> Subject: [ESS] Xemacs+ESS problem under Windows
>
> hi John,
> >
> > Invalid read syntax: "Cannot read unreadable object"
> >
> > I traced the error to the following code in ess-site.el
>
> You've tracked the error down to some code that Rich and I
> added recently (in the last months); is there any chance
> that you could generate a *Backtrace* buffer that might give
> us more clues as to what is generating this erorr?
>
> ----
> If Emacs reports an error, backtraces can help us debug
> the problem.
> Type "M-x set-variable RET debug-on-error RET t RET". Then
> run the command that causes the error and you should see a
> *Backtrace* buffer containing debug information; send us that buffer.
> ----
>
> In the meantime, commenting out the code would not be a big
> loss -- this section of code adds some extra menu items that
> allows, e.g. R-1.8.1 to be called rather than just R.
>
> Stephen
More information about the ESS-help
mailing list