[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacsclient's option decoding code

From: Stefan Monnier
Subject: Re: emacsclient's option decoding code
Date: Wed, 12 Nov 2008 10:56:05 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

>> I don't like using nil for "the w32 window system", indeed.  I think the
>> "" we currently use is better.
> It's not really important, but I don't understand why "" would be
> better.

You might be right.  I tend to think of `display' as something similar
to `terminal', but they're not the same.  To tell you the truth, I'm not
sure what `display' is meant for exactly.

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".

> and the generalization of nil meaning "the current display" for all
> environments, not just Windows, seems more fitting.

The current display should be obtained via (frame-parameter nil 'display).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]