I'm using the XFree86 stuff to run my bash shells on cygwin and am using the
following to start my X session.
xinit -- Xwin -clipboard -multiwindow &
[I've tried various combinations of -multiwindow and -rootless]
In multiwindow mode xterms only seem to have keyboard focus if the mouse is
in
the
- Original Message -
From: "Harold L Hunt II"
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 04, 2004 3:43 PM
Subject: Re: XWin -clipboard and xterm focus -#- MailID:8WBA
> Peter,
>
> You need to do a general update of Cygwin by rerunning Cygwin's
> setup.exe and letting it upgrade updat
eleases.
>
> If you still have the same problems after upgrading, feel free to reask
> your questions.
>
> Harold
>
> Peter Wisnovsky wrote:
>
> > I'm using the XFree86 stuff to run my bash shells on cygwin and am using
the
> > following to start my X sess
> > I updated, and it seems to have removed all the files associated with
> > xwinclip, but not replaced them with any working functionality in XWin.
So
> > now I have NO working clipboard support after this update. The focus
problem
> > still exists as well. Sigh.
>
> That is precisely what was su
PM
Subject: Re: XWin -clipboard and xterm focus -#- MailID:JWBA
> Peter Wisnovsky wrote:
> >>>I updated, and it seems to have removed all the files associated with
> >>>xwinclip, but not replaced them with any working functionality in XWin.
> >
> > So
> >
&
Message -
> > From: "Harold L Hunt II"
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, March 04, 2004 5:42 PM
> > Subject: Re: XWin -clipboard and xterm focus -#- MailID:JWBA
> >
> >
> >
> >>Peter Wisnovsky wrote:
&g
04 10:59 AM
Subject: Re: XWin -clipboard and xterm focus -#- MailID:KYBA
> Peter,
>
> Sounds like cygwin1.dll was in use when you updated and that you have to
> reboot in order for it to be actually replaced.
>
> Either that (try the reboot first) or you have an older copy of
>
use startxwin.bat from the XFree86-startup-scripts package.
> It is much more reliable and easy to understand. I think it would
> help in your case to at least try startxwin.bat to confirm that it works
> as expected, then you can work on fixing your startup method of choice.
>
> Harold
>
> Peter Wisnovsky wrote:
> I would just use startxwin.bat from the XFree86-startup-scripts package.
> It is much more reliable and easy to understand. I think it would
> help in your case to at least try startxwin.bat to confirm that it works
> as expected, then you can work on fixing your startup method of choice.
I'v
