You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 >
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).
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.
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?
Tracking back, it seems to be happening here:
The text was updated successfully, but these errors were encountered: