ESS question

Rodney Sparapani rsparapa at
Fri Oct 19 20:08:02 CEST 2001


There are several issues surrounding color coding which is by far the most 
complicated thing that emacs and ESS does.  First of all, older versions of 
emacs have lots of problems.  ESS 5.1.19 has resolved some issues related to 
older versions of emacs and ESS' wrong/incomplete colorization.  You can get the 
latest functionality by placing the following in ~/.emacs:

(setq ess-sas-run-make-regexp nil)
(require 'ess-site "~/ess/lisp/ess-site")

Finally, the way that emacs color codes things during an edit is on a single 
line basis.  In other words, if something you are working on, like a long 
comment, is wrapped over many lines, emacs doesn't try to look ahead.  It only 
does that when it reads the whole file.  This behavior is general, but can be 
aggravated by fast-lock or lazy-lock.  I use fast-lock, but haven't had success 
with lazy-lock.  YMMV

Rodney Sparapani              Medical College of Wisconsin
Sr. Biostatistician           Patient Care & Outcomes Research (PCOR)
rsparapa at    
Was 'Name That Tune' rigged?  WWLD -- What Would Lombardi Do

>Date: Fri, 19 Oct 2001 13:57:15 -0400 (EDT)
>From: Sue Rosenkranz <sue at>
>To: ESS-bugs at
>cc: Evan Caten <caten at>
>Subject: ESS question
>MIME-Version: 1.0
>We have a question re: ESS.  When editing a SAS file, the color coding is 
>NOT updated when you make a change to an existing hunk of code (if you
>un-comment out, for example, the lines remain red).
>Is there a command we can issue that says, "re-ESS the whole file now"?

ess-help mailing list -- To (un)subscribe, send
subscribe	or	unsubscribe
(in the "body", not the subject !)  To: ess-help-request at

More information about the ESS-help mailing list