Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS Windows anyone? #168

Open
Symbolics opened this issue May 3, 2020 · 2 comments
Open

MS Windows anyone? #168

Symbolics opened this issue May 3, 2020 · 2 comments

Comments

@Symbolics
Copy link

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
Copy link
Member

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
Copy link
Author

Symbolics commented May 11, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants