Re: zkbd on OS X

[Mikael Magnusson <mikachu@xxxxxxxxx>]

On 3 January 2012 11:16, Phil Pennock
<zsh-workers+phil.pennock@xxxxxxxxxxxx> wrote:
> On 2012-01-02 at 16:57 -0200, Daniel Serodio (lists) wrote:
>> Since 4.3.5 or so[1], zkbd uses ${DISPLAY:-$VENDOR-$OSTYPE} instead of
>
>> Has anyone had this problem before? Am I doing something wrong?
>
> You're not doing anything wrong; it was an Xorg/XFree86 assumption about
> the value of $DISPLAY, ":0", ":0.0", "hostname:0" or the like.
> ("hostname:displaynumber.screennumber").  I think that this might be an
> X11 requirement ...
>
> On MacOS, it's a Unix-domain socket, used by launchd to dynamically
> start up the X11 server when a client opens the socket, and hand off to
> the running server.  From an X point of view, this should still have
> been exposed as ":0" and the local transport could have been chosen
> behind the scenes to be via a Unix-domain socket which triggers the
> launchd behaviour.  Alas, Mac's are gratuitously different here.
>
> How about:
> ----------------------------8< cut here >8------------------------------
> if [[ -z "$DISPLAY" || $DISPLAY == */* ]]; then
>  termID="$VENDOR-$OSTYPE"
> else
>  termID="$DISPLAY"
> fi
> ----------------------------8< cut here >8------------------------------

Why does zkbd use $DISPLAY at all? Why would I be getting different
sequences for urxvt in :1 than in :0? Or have to set everything up
separately when the display number changes?

-- 
Mikael Magnusson