Re: wl_display_connect() falling back to wayland-0

2013-12-12 Thread Pekka Paalanen
On Wed, 11 Dec 2013 11:16:22 -0800 Bill Spitzak wrote: > I certainly like that there is a fallback. The user should not have > to set environment variables to get something to work. Exactly. Users will not have to anyway. All the environment variables are already set by "the system", unless the

Re: wl_display_connect() falling back to wayland-0

2013-12-11 Thread Bill Spitzak
I certainly like that there is a fallback. The user should not have to set environment variables to get something to work. In our software using X we always check if DISPLAY is set and if not set it to ":0". This is so the program just works even if the user's setup is wrong. (The primary reas

Re: wl_display_connect() falling back to wayland-0

2013-12-11 Thread Jason Ekstrand
Hi Emilio, On Dec 9, 2013 6:38 AM, "Emilio Pozuelo Monfort" wrote: > > Hi, > > I was looking at making gtk+ try the wayland backend before the x11 one [1]. > This would solve the problem where every gtk+ app uses the x11 backend through > XWayland when the latter is available. > > As you can read

wl_display_connect() falling back to wayland-0

2013-12-09 Thread Emilio Pozuelo Monfort
Hi, I was looking at making gtk+ try the wayland backend before the x11 one [1]. This would solve the problem where every gtk+ app uses the x11 backend through XWayland when the latter is available. As you can read on comment #3 and in the patch from comment #1, wl_display_connect() currently fal