public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Configuration for multiple monitors
Date: Sat, 10 Jan 2004 16:38:00 -0000 [thread overview]
Message-ID: <40002A72.3060801@msu.edu> (raw)
In-Reply-To: <1073640179.8704.4.camel@famine>
Ãyvind,
Jack Tanner had some valid points for keeping -nomultiplemonitors.
The reason we won't just remove the -multiplemonitors option is a little
easier:
1) XWin.exe does not print nor popup error messages when it exists;
rather, it logs them to /tmp/XWin.log.
2) Removing the -multiplemonitors option will cause XWin.exe to fail to
start.
3) Must users do not know to look at /tmp/XWin.log to see that they
passed an invalid parameter.
4) We will start seeing lots of fun reports on the mailing list asking
why XWin.exe is crashing on startup, when it is in fact just reporting
that -multiplemonitors is an invalid parameter.
That is why we don't remove old parameters completely. We don't want to
waste time debugging non-problems caused by doing so.
Harold
Ãyvind Harboe wrote:
> Harold,
>
> perhaps the below should *always* be TRUE and there shouldn't be
> an option at all?
>
> g_ScreenInfo[i].fMultipleMonitors = TRUE;
>
> If so, then the changes TBD are:
>
> - remove the -multiplemontiors option
> - always set fMultipleMonitors=TRUE, or remove fMultipleMontiors altogether.
>
> (Code removed is not code deleted; it is in CVS in case it needs to be summoned
> at some point.)
>
>
> Thanks for these tips BTW:
>
> http://www.cygwin.com/ml/cygwin-xfree/2004-01/msg00160.html
>
> Ãyvind
>
>
>
next prev parent reply other threads:[~2004-01-10 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 9:23 Øyvind Harboe
2004-01-09 18:59 ` Jack Tanner
2004-01-10 16:34 ` Harold L Hunt II
2004-01-10 16:38 ` Harold L Hunt II [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 17:47 Øyvind Harboe
2004-01-08 18:12 ` Harold L Hunt II
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=40002A72.3060801@msu.edu \
--to=huntharo@msu.edu \
--cc=cygwin-xfree@cygwin.com \
/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.
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).