[Openmcl-devel] ...the sky is falling
joakim at joakimsandgren.com
Tue Apr 6 11:55:58 UTC 2010
Thank you Gary.
It is now half the way.
I come to the right document but lisp still say Couldn't find
definition for... and it dont go to the definition.
But I dont have the console anymore.
It also opens the file window in another place than where it was
saved. And the title is always in uppercase letters (and the files
name is in lower case letters).
In the old version 13560 the console does the same: open in a new
location with uppercase letters. when I quitted the console the window
popped back to its
original location and changed the title to lowsercase letters.
With the "fixed" file (the file where I did paste the totality of the
original file) I still come to the definition in the 2 versions.
That windw is still though the uppercase letter window in a new
This is perhaps a wanted behaviour, I just wanted to point it out..
Le 6 avr. 10 à 11:53, Gary Byers a écrit :
> On Fri, 2 Apr 2010, Joakim Sandgren wrote:
>> here is one console :sincerely
> Thanks. I haven't been able to reproduce this, but can convince
> that a bug that I did find could have led to this error. Could you
> update to r13585 (in the trunk), rebuild the IDE, and let me know if
> problem persists ?
> I think that the combination of factors that might lead to the bug is:
> - the definition you're looking for isn't at its recorded position in
> the file/buffer, either because the file/buffer has been edited
> the function was defined or because that position is a byte offset
> a character offset) and the file is encoded in a variable-length
> (like UTF-8). (I don't remember if the latter possibility is a
> Gail might know offhand.) In this case, M-. has to search for the
> - a data structure used to perform that search was initialized
> if the length of the search string (the recorded source of the
> was greater than the largest CHAR-CODE of the characters in that
> string. (In other words, it was completely bogus.)
> That (mis-)initialization is definitely a bug, and it would have led
> to the
> same symptom that showed up in the backtrace.
> When reporting a bug, it's much, much better to send a backtrace
> (even if
> it turns out to be unnecessary) than to not send one (if it does
> turn out
> to be necessary.) r13585 fixes -a- bug (and it's quite possible
> that it's
> the one that's affected you), and it wouldn't have been possible to
> know where to look without the backtrace.
joakim sandgren musik
42, rue de Maubeuge
+33 (0)1 45 26 43 90
info at joakimsandgren.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel