unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: dann@ics.uci.edu, emacs-pretest-bug@gnu.org, monnier@iro.umontreal.ca
Subject: Re: 23.0.50; DISPLAY env var bug on w32?
Date: Sun, 13 Jan 2008 06:17:35 +0200	[thread overview]
Message-ID: <ud4s6qrz4.fsf@gnu.org> (raw)
In-Reply-To: <478902B8.30908@gmail.com> (lennart.borgman@gmail.com)

> Date: Sat, 12 Jan 2008 19:11:04 +0100
> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
> CC: Eli Zaretskii <eliz@gnu.org>, emacs-pretest-bug@gnu.org, 
>  dann@ics.uci.edu, monnier@iro.umontreal.ca
> 
> David Kastrup wrote:
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> >>> Date: Sat, 12 Jan 2008 16:59:22 +0100
> >>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
> >>> CC: dann@ics.uci.edu, emacs-pretest-bug@gnu.org, 
> >>>  monnier@iro.umontreal.ca
> >>>
> >>> But what about multiple displays on w32?
> >> What do you mean by ``multiple displays on w32''?  The -d DISPLAY
> >> feature that is standard on X is not supported by Windows.
> > 
> > What about people running an X server on Windows?  Like that from Cygwin
> > or Xceed or so?
> 
> Beside that you can have multiple monitors on w32 too, but I do not know 
> anything about that.

The -d DISPLAY option is not the right mechanism for supporting that,
unless someone teaches the Windows port of Emacs how to do that.
Right now, using -d DISPLAY on Windows causes nothing but trouble.

  reply	other threads:[~2008-01-13  4:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 18:45 23.0.50; DISPLAY env var bug on w32? Lennart Borgman (gmail)
2008-01-07 21:03 ` Dan Nicolaescu
2008-01-08  0:28   ` Lennart Borgman (gmail)
2008-01-08  2:58     ` David De La Harpe Golden
2008-01-12 15:51     ` Eli Zaretskii
2008-01-12 15:59       ` Lennart Borgman (gmail)
2008-01-12 16:24         ` Eli Zaretskii
2008-01-12 18:06           ` David Kastrup
2008-01-12 18:11             ` Lennart Borgman (gmail)
2008-01-13  4:17               ` Eli Zaretskii [this message]
2008-01-13  4:30                 ` Juanma Barranquero
2008-01-13  6:55                   ` Eli Zaretskii
2008-01-13 21:41                     ` Stefan Monnier
2008-01-14  4:07                       ` Eli Zaretskii
2008-01-14 15:04                         ` Stefan Monnier
2008-01-14 15:13                           ` Jason Rumney
2008-01-14 20:33                             ` Eli Zaretskii
2008-01-14 23:19                               ` Jason Rumney
2008-01-15  4:11                                 ` Eli Zaretskii
2008-01-15 22:11                                   ` Jason Rumney
2008-01-13  4:16             ` Eli Zaretskii
2008-01-07 21:13 ` Robert J. Chassell
2008-01-07 21:23   ` Eli Zaretskii
2008-01-07 21:24 ` Eli Zaretskii
2008-01-07 21:32   ` Lennart Borgman (gmail)

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ud4s6qrz4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=lennart.borgman@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).