MS Windows anyone?

[Symbolics]

Has anyone got CLX to work on MS Windows? I get the following error for all values of DISPLAY I tried. Using VcXsrv without any problem with several remote machines. Checked authorisation, etc. No errors reported by the X server. Any ideas?

? (ql:quickload 'clx)
To load "clx":
  Load 1 ASDF system:
    clx
; Loading "clx"

(CLX)
? (ql:quickload 'clx/demo)
To load "clx/demo":
  Load 1 ASDF system:
    clx/demo
; Loading "clx/demo"
..................................................
[package xlib-demo/clclock]
> Error: Connection failure to X0.0 server 127.0.0.1 display 0:
> While executing: XLIB::X-ERROR, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.
1 >

Tracking back, it seems to be happening here:

1 > :f 1
 (22D882C8) : 1 (DISPLAY-CONNECT #<DISPLAY 127.0.0.1:0 ( R0)> :AUTHORIZATION-NAME "" :AUTHORIZATION-DATA "") 1629
  (XLIB:DISPLAY &KEY :AUTHORIZATION-NAME :AUTHORIZATION-DATA)
   XLIB:DISPLAY: #<DISPLAY 127.0.0.1:0 ( R0)>
   XLIB::AUTHORIZATION-NAME: ""
   XLIB::AUTHORIZATION-DATA: ""

  XLIB::REPLY-BUFFER: #S(XLIB::REPLY-BUFFER :SIZE 4096 :IBUF8 #(0 0 0 0 0 ...) ...)
  XLIB::BUFFER-BBUF: #(0 0 0 0 0 ...)
  XLIB::SUCCESS: NIL
  XLIB::REASON-LENGTH: 0
  XLIB::MAJOR-VERSION: 0
  XLIB::MINOR-VERSION: 0
  XLIB::TOTAL-LENGTH: 0
  XLIB::VENDOR-LENGTH: NIL
  XLIB::NUM-ROOTS: NIL
  XLIB::NUM-FORMATS: NIL

[dkochmanski]

Hey. Did you check if your environment variables indicate a correct display? I remember someone had an issue where emacs compiled on different machine "saved" the environment variable, so clx couldn't open the display (because on the user machine it was different).

[Symbolics]

The display from the MSYS2 shell is correct. Any way to check this from within lisp?

On Sunday, May 10, 2020, 8:25:27 PM GMT+8, Daniel Kochmanski <[email protected]> wrote:  

Hey. Did you check if your environment variables indicate a correct display? I remember someone had an issue where emacs compiled on different machine "saved" the environment variable, so clx couldn't open the display (because on the user machine it was different).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.