I forgot to mention that XF86Config support is disabled in this release.
It may be possible to get XF86Config support building again, but
Alexander recently added some command-line options that should be a
useable replacement for most users. In addition, the keyboard
autoconfiguration seems
Alexander, dont you think startxwin.bat should exit
if XWin fails to start ?
This should be pretty easy to support in a batch file :
start XWin -multiwindow
if not errorlevel 0 goto badexit
--- Kris Thielemans [EMAIL PROTECTED] a écrit :
This is normal behaviour.
well, I doubt that you
- Forwarded message from Ross Boulet rboulet -
From: Ross Boulet
To: Cygwin
Subject: Man not finding pages
Date: Sat, 28 Feb 2004 16:06:22 -0600
I solved my own problem with man not finding pages but in doing the research
on it, I found something I thought might be worthy of mentioning.
Sylvain Petreolle wrote:
Alexander, dont you think startxwin.bat should exit
if XWin fails to start ?
This should be pretty easy to support in a batch file :
start XWin -multiwindow
if not errorlevel 0 goto badexit
Won't work. start launches XWin, then returns to the batch shell
immediately.
Well I'll be dipped in shit.
Ain't that the weirdest thing you ever heard of? Now I gotta go revert
that script and put a proper note in there so that no one tries to fix
it like I did.
Harold
Christopher Faylor wrote:
- Forwarded message from Ross Boulet rboulet -
From: Ross Boulet
A few issues I've encountered with Cygwin/X 4.3.0-47:
Issue #1:
In multiwindow mode, XWin doesn't reset when the last client exists.
Example:
XWin :9 -terminate -multiwindow sleep 5; DISPLAY=:9 xhost
XWin should terminate after 5 seconds, but it remains running.
It isn't supposed to. Run
On 2004-02-28 21:07, Harold L Hunt II wrote:
In multiwindow mode, XWin doesn't reset when the last client exists.
It isn't supposed to. Run 'twm' as your window manager and you will
see that the X Server does not reset when the last non-window manager
client exits; this is because the window
Eran,
As for preventing multiple instances of XWin, a kludgy way to do it is
by checking if anyone is listening on the X server port, using NETSTAT.
Example:
This feature is already implemented in my local tree (not
port based but mutex based detection). It is in test and
documentation
Eran Tromer wrote:
On 2004-02-28 21:07, Harold L Hunt II wrote:
In multiwindow mode, XWin doesn't reset when the last client exists.
It isn't supposed to. Run 'twm' as your window manager and you will
see that the X Server does not reset when the last non-window manager
client exits; this is
Takuma Murakami wrote:
Eran,
As for preventing multiple instances of XWin, a kludgy way to do it is
by checking if anyone is listening on the X server port, using NETSTAT.
Example:
This feature is already implemented in my local tree (not
port based but mutex based detection). It is in test
Oh, I also forgot to mention that this is a test release, so I need
people to report on how well it works before I can mark it a the current
version.
Harold
i've downloaded the latest X server, and clipboard integration
is still failing for me, hanging my X application (xmh on a
remote machine) as soon as i select something. if i don't
use -clipboard, then xwinclip still works ok, with it's known
problems.
let me know if i can provide more info to
12 matches
Mail list logo
