[ESS] Introducing Polymode

[Mathieu Basille]

Well, this one was difficult to isolate... From what I understand, this is 
the use of double brackets, such as [[i]] in a R code chunk that is the 
origin of the error messages. Then, the error messages arise every time a R 
code chunk is 'parsed' by Emacs (sorry if this is not the correct 
terminology: at startup, only the chunks on screen are affected, but moving 
the cursor to another code chunk makes a new message).

And the number in the jit-lock-function seems to be related to some sort of 
character counter (from the beginning of the file).

I attach a simple, although quite wordy, example. I just added enough Lorem 
ipsum to make sure that one R code chunk was not on screen after we open 
the file. See the first chunk with [[i]].

Mathieu.


Le 03/29/2013 11:30 AM, Vitalie Spinu a écrit :
>    >> Mathieu Basille <basille at ase-research.org>
>    >> on Fri, 29 Mar 2013 11:17:00 -0400 wrote:
>
>   > Error during redisplay: (jit-lock-function 1) signaled (wrong-type-argument
>   > stringp nil)
>   > Error during redisplay: (jit-lock-function 522) signaled (wrong-type-argument
>   > stringp nil)
>
>   > And from time to time (but I can't seem to find the pattern when it occurs), I
>   > have the same error message, but for functions 110, 682, 1042, 1201, 1561, 1720,
>   > 2591...
>
>   > I really don't know if this is problematic, since I can't see any troubles with
>   > it...
>
> In a perfect world you should not see these messages. They come from
> font-lock and are notoriously difficult to debug. Can you please send me
> a small reproducible example where this happens? I will add it to the
> test cases.
>
>      Vitalie
>
>

-- 

~$ whoami
Mathieu Basille, PhD

~$ locate --details
University of Florida \\
Fort Lauderdale Research and Education Center
(+1) 954-577-6314
http://ase-research.org/basille

~$ fortune
« Le tout est de tout dire, et je manque de mots
Et je manque de temps, et je manque d'audace. »
  -- Paul Éluard