public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Brian Ford <ford@vss.fsi.com> To: fergus@bonhard.uklinux.net Cc: cygwin-xfree@cygwin.com Subject: Re: Portable Cygwin works, but XWin fails Date: Thu, 11 Dec 2003 01:32:00 -0000 [thread overview] Message-ID: <Pine.GSO.4.58.0312101737100.28297@eos> (raw) In-Reply-To: <000501c3bf73$844a6c40$0b7b2852@leper> On Wed, 10 Dec 2003 fergus@bonhard.uklinux.net wrote: > Brian Ford wrote: > > No, you don't need to. Just Xwin.exe -nolisten local. > > Thank you. This worked just fine. I take the point about Google-ing - that's > how I learned that diverting tmp/XWin.log might help. I didn't see the > "-nolisten local" advice ... > I found both in the same message, although it is older than I stated: http://sources.redhat.com/ml/cygwin-xfree/2002-07/msg00165.html > Just one final question: when I get into rxvt after "XWin -nolisten > local -multiwindow &", the keyboard suddenly becomes USA, whereas it is set > (correctly) to UK otherwise, within bash, within rxvt and for that matter > within Windows. In this case, when I exit rxvt back to bash, the UK keyboard > is recovered. > I think the message listed above has another hint for you about this :). > Does the "-nolisten local" switch impose some kind USA default, as it would > indeed appear to do? > No, not related at all. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
next prev parent reply other threads:[~2003-12-10 23:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-10 21:37 fergus 2003-12-10 21:45 ` Harold L Hunt II 2003-12-10 22:18 ` Brian Ford 2003-12-10 22:43 ` fergus 2003-12-10 22:58 ` Brian Ford 2003-12-10 23:41 ` fergus 2003-12-11 1:32 ` Brian Ford [this message] 2003-12-11 7:43 ` Alexander Gottwald 2003-12-10 22:30 fergus 2003-12-10 23:15 ` Brian Ford 2003-12-11 7:26 Pille Geert (bizvdm) 2003-12-11 21:58 fergus 2003-12-12 16:46 ` Rasjid Wilcox
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=Pine.GSO.4.58.0312101737100.28297@eos \ --to=ford@vss.fsi.com \ --cc=cygwin-xfree@cygwin.com \ --cc=fergus@bonhard.uklinux.net \ /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: linkBe 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).