Re: emacsclient's option decoding code

[Lennart Borgman]

On Wed, Nov 12, 2008 at 5:37 PM, Juanma Barranquero <address@hidden> wrote:
>> E.g., let's imagine a w32 version of Emacs which has been hacked to be
>> able to use X11 as well.  And let's additionally say that it can even
>> also use GNUstep, so it can have w32, x11, and ns frames, all displayed
>> on the same screen.  Both ns and x11 frames will have a `display' set to
>> the same value (typically ":0.0" or something along these lines),
>> whereas the w32 frames's display will be "" (or nil, or ...).
>> This discrepency doesn't seem good.
>>
>> So maybe we should just make w32 use display=":0.0".
>
> Fine by me. Someday, if multi-GUI materializes, we'll have to add a
> frame parameter or another way for lisp code to query the GUI
> associated with a given frame.

I do not understand this discussion at all, but is there anything
preventing using a value that has the string "w32" in it instead of
just ":0.0"? It seems to me that would be easier to understand.