Custom Query (1030 matches)

People have reported that it can be prohibitively slow to call SET-MACRO-CHARACTER on all potential Unicode characters.

I'm not surprised by this, but I'm not sure that there's a good reason to make it impractical for someone who wants to do this to do so, either.

changing the data structures that CCL uses to associate characters with functions can affect things like SET-SYNTAX-FROM-CHAR and COPY-READTABLE as well as SET-MACRO-CHARACTER and (poossibly) SET-DISPATCH-MACRO-CHARACTER.

Hi,

It looks like there's a mismatched #ifndef/#endif pair in ccl/lisp-kernel/lisp-debug.c for Windows here:

    void
    redirect_debugger_io()
    {
    #ifndef WINDOWS
      if (1 || !isatty(fileno(dbgin))) {
        int fd = open("/dev/tty", O_RDWR);
        if (fd >=0) {
          dbgin=fdopen(fd,"r");
          open_debug_output(fd);
        }
    #endif   <--- too soon?
      }
    }

This causes the build to fail with:

x86_64-w64-mingw32-gcc -include ../platform-win64.h -c ../lisp-debug.c -DWIN_64 -DWINDOWS -D_REENTRANT -DX86 -DX8664 -D_GNU_SOURCE -DHAVE_TLS -DEMUTLS -DTCR_IN_GPR -DSVN_REVISION="16387" -g -O2 -Wno-format  -m64 -o lisp-debug.o
../lisp-debug.c:234:1: error: expected identifier or '(' before '}' token
 }
 ^
Makefile:74: recipe for target 'lisp-debug.o' failed
make: *** [lisp-debug.o] Error 1

I think the #endif just needs to come after the subsequent }. After moving it the build seems to succeed for me.

Thanks,

Jared

Open a largish file, e.g. cocoa-editor.lisp

Right click in it and select Duplicate this window.

Go back to the first window and scroll it down to near the end, and click somewhere in the text.

Go back to the second window, and scroll by large amounts and try to click in the text. For me, most of the time, clicking places the insertion point in an apparently random location in the buffer, instead of where I clicked.