From: "Lennart Borgman" <lennart.borgman@gmail.com>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: cyd@stupidchicken.com, Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: emacsclient's option decoding code
Date: Thu, 13 Nov 2008 02:16:20 +0100 [thread overview]
Message-ID: <e01d8a50811121716i46166966l2fdc659a3ee03de@mail.gmail.com> (raw)
In-Reply-To: <f7ccd24b0811120837r4a055b92w3b543d36c427ec58@mail.gmail.com>
On Wed, Nov 12, 2008 at 5:37 PM, Juanma Barranquero <lekktu@gmail.com> 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.
next prev parent reply other threads:[~2008-11-13 1:16 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 14:04 emacsclient's option decoding code Eli Zaretskii
2008-11-02 2:13 ` Stefan Monnier
2008-11-02 21:45 ` Chong Yidong
2008-11-02 22:00 ` Juanma Barranquero
2008-11-02 23:18 ` Chong Yidong
2008-11-03 0:50 ` Juanma Barranquero
2008-11-03 4:14 ` Eli Zaretskii
2008-11-03 12:12 ` Juanma Barranquero
2008-11-03 20:06 ` Eli Zaretskii
2008-11-03 20:19 ` Chong Yidong
2008-11-04 4:20 ` Eli Zaretskii
2008-11-04 16:40 ` Chong Yidong
2008-11-06 11:56 ` Juanma Barranquero
2008-11-03 21:26 ` Juanma Barranquero
2008-11-04 4:19 ` Eli Zaretskii
2008-11-06 12:08 ` Juanma Barranquero
2008-11-07 9:53 ` Eli Zaretskii
2008-11-07 11:42 ` Juanma Barranquero
2008-11-07 11:47 ` Juanma Barranquero
2008-11-07 14:36 ` Eli Zaretskii
2008-11-07 14:42 ` Juanma Barranquero
2008-11-10 18:22 ` Juanma Barranquero
2008-11-10 18:36 ` Chong Yidong
2008-11-10 23:33 ` Juanma Barranquero
2008-11-11 4:09 ` Eli Zaretskii
2008-11-11 4:14 ` Chong Yidong
2008-11-11 21:16 ` Eli Zaretskii
2008-11-11 9:39 ` Juanma Barranquero
2008-11-11 15:37 ` Juanma Barranquero
2008-11-11 21:24 ` Eli Zaretskii
2008-11-11 23:36 ` Juanma Barranquero
2008-11-12 4:22 ` Eli Zaretskii
2008-11-12 9:41 ` Juanma Barranquero
2008-11-12 19:14 ` Eli Zaretskii
2008-11-12 21:05 ` Juanma Barranquero
2008-11-13 4:12 ` Eli Zaretskii
2008-11-13 8:34 ` Juanma Barranquero
2008-11-12 19:37 ` Eli Zaretskii
2008-11-12 2:31 ` Stefan Monnier
2008-11-12 9:33 ` Juanma Barranquero
2008-11-12 15:56 ` Stefan Monnier
2008-11-12 16:37 ` Juanma Barranquero
2008-11-12 17:13 ` Stefan Monnier
2008-11-13 1:16 ` Lennart Borgman [this message]
2008-11-13 4:18 ` Eli Zaretskii
2008-11-13 9:00 ` Juanma Barranquero
2008-11-13 15:45 ` Dan Nicolaescu
2008-11-13 16:05 ` Juanma Barranquero
2008-11-13 16:05 ` Juanma Barranquero
2008-11-13 16:08 ` Dan Nicolaescu
2008-11-12 19:36 ` Eli Zaretskii
2008-11-12 20:56 ` Stefan Monnier
2008-11-13 4:10 ` Eli Zaretskii
2008-11-13 4:29 ` mail
2008-11-13 20:54 ` Eli Zaretskii
2008-11-13 21:27 ` mail
2008-11-13 22:30 ` Eli Zaretskii
2008-11-13 23:54 ` mail
2008-11-13 20:03 ` Juri Linkov
2008-11-13 20:40 ` mail
2008-11-13 21:08 ` Thorsten Bonow
2008-11-13 22:01 ` Thorsten Bonow
2008-11-15 2:58 ` Evil Boris
2008-11-07 14:35 ` Eli Zaretskii
2008-11-03 14:45 ` Juanma Barranquero
2008-11-03 19:59 ` Eli Zaretskii
2008-11-03 20:03 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a50811121716i46166966l2fdc659a3ee03de@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.