Charles Wilson wrote:
Is there a way to test run-2.0? What is the syntax to replace:
C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe
Sure:
and how to replace
C:\cygwin-2\bin\run.exe bash -l -c 'rm -rf /tmp/{.X*,dbus*,orbit*,*};
XWin -nowgl -multiwindow -clipboard -sile
On 8/1/2013 7:19 AM, Angelo Graziosi wrote:
Charles Wilson wrote:
Is there a way to test run-2.0? What is the syntax to replace:
C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe
Sure:
and how to replace
C:\cygwin-2\bin\run.exe bash -l -c 'rm -rf /tmp/{.X*,dbus*,orbit*,*
On 01/08/2013 01:55, Jeremy Elson wrote:
> I recently upgraded from the 32-bit to the 64-bit build of Cygwin
> 1.7.22 on Windows 8 x64. For the most part, everything works
> identically (except faster!). But I have noticed one problem: xterm no
> longer seems to respond to the magic escape codes th
On Thu, Aug 1, 2013 at 10:28 AM, Jon TURNEY wrote:
> On 01/08/2013 01:55, Jeremy Elson wrote:
> > I recently upgraded from the 32-bit to the 64-bit build of Cygwin
> > 1.7.22 on Windows 8 x64. For the most part, everything works
> > identically (except faster!). But I have noticed one problem: xte
Charles Wilson wrote:
(I'm not sure why you need & at all; unless it allows the bash shell to exit,
where otherwise it would hang around?)
Without the "&", there is an extra bash process running: I want just to
start XWin...
See attached.
>
http://www.w3.org/2001/XMLSchema-instance";;
See below...
On 8/1/2013 2:33 PM, Angelo Graziosi wrote:
> Charles Wilson wrote:
>> (I'm not sure why you need & at all; unless it allows the bash shell to
>> exit, where otherwise it would hang around?)
>
> Without the "&", there is an extra bash process running: I want just to
> start XWin...
