ess-mode 5.2.0; void-variable comint-last-input-end

john.gavin at john.gavin at
Thu May 27 12:45:02 CEST 2004

Hi Stephen,

By going through my init.el file line by line
I believe that I have resolved my problem.

My init.el file ends with
(based on some code originally from John Fox)

(setq win1 (selected-window))  ; win1 is on top
(setq win2 (split-window-horizontally)) ; win2 is on the bottom
(select-window win2)
(R) ; start R in win2 -- assumes that the R bin directory is on the path
; window win2 dedicated to R process
(if dedicated-R-window (set-window-dedicated-p win2 t)) 
(select-window win1) ; back to win1
(R-mode) ; put *scratch* buffer in R mode ; FAILS with latest ESS version

The last line 

(R-mode) ; put *scratch* buffer in R mode ; FAILS with latest ESS version

caused my error.
As I dont use the scratch window, I have commented it out
and things seem to be back to normal.
(Ideally, I should prevent the scratch window
from opening in the first place.)

Sorry for having consumed bandwidth/time with this.



John Gavin <john.gavin at>,
Quantitative Risk Models and Statistics,
UBS Investment Bank, 6th floor, 
100 Liverpool St., London EC2M 2RH, UK.
Phone +44 (0) 207 567 4289
Fax   +44 (0) 207 568 5352

> -----Original Message-----
> From: Stephen Eglen [mailto:stephen at]
> Sent: 27 May 2004 10:16
> To: Gavin, John
> Cc: ess-help at
> Subject: ess-mode 5.2.0; void-variable comint-last-input-end
> Dear John
>  > I am trying to upgrade to ESS 5.2.0 (from 5.1.24) 
>  >
>  > but when I start XEmacs and 
>  > each time I send a line to the R process I get the error
>  > 
>  > (error/warning) Error in process filter: (void-variable
>  > comint-last-input-end)
>  > 
>  > I dont have 'comint-last-input-end' in my init.el file
>  > so I assume that it is something new in 5.2.0.
>  > Has anyone else encountered this problem?
> This is odd, and I don't see this variable used in the lisp source.
> From the "Reporting Bugs" part of the manual:
> ----------------------------------------------------------------------
>    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.
> ----------------------------------------------------------------------
> Please could you send us a *Backtrace* buffer if you get one.
>  > 
>  > It tried to browse 
>  >
>  > for a solution without success.
>  > (Is there a better way to search the archieves?)
> Actually, you've just shown me a nicer way to search the archives than
> I knew before -- at the bottom of the URL you sent me I see a green
> "Search" box.
> Thanks,
> Stephen

Visit our website at

This message contains confidential information and is intend...{{dropped}}

More information about the ESS-help mailing list