On Fri, Nov 20, 2009 at 4:25 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
On 13/11/2009 03:14, Ken Brown wrote:
On 11/12/2009 3:17 PM, Jon TURNEY wrote:
On 10/11/2009 23:44, Mike Ayers wrote:]
Apparently, run.exe is not providing stdout/stderr to dump to. The
workaround:
[SNIP]
gvim do output some error string it is
stopped by run.exe
so as said in next reply
C:\cygwin\bin\run.exe -p /usr/bin sh -c gvim /dev/null 21 is a workaround
thanks
JLM
On Tue, Nov 10, 2009 at 7:03 AM, Linda Walsh cyg...@tlinx.org wrote:
jean-luc malet wrote:
thanks for the reply
and then gvim try to open
c:omeatho.file.
please can someone give a fix to run.exe so that the process is run
with stdout and stderr redirected to /dev/null?
thanks
JLM
On Mon, Nov 16, 2009 at 5:04 PM, jean-luc malet jeanluc.ma...@gmail.com wrote:
thanks for the reply
I tested doing
c
[mailto:cygwin-xfree-
ow...@cygwin.com] On Behalf Of jean-luc malet
Sent: Thursday, November 05, 2009 6:18 AM
gvim.bat :
c:\cygwin\bin\run -p /bin gvim
Try:
c:\cygwin\bin\run -p /bin:/usr/X11R6/bin gvim
HTH,
Mike
--
KISS! (Keep It Simple, Stupid!)
(garde le simple
)
normally all X operation shall be protected with mutexes
any idea?
thanks
JLM
-- Forwarded message --
From: jean-luc malet jeanluc.ma...@gmail.com
Date: Fri, Jul 24, 2009 at 11:12 AM
Subject: Re: strange behavior with threads...
To: cyg...@cygwin.com
On Thu, Jul 23, 2009 at 4:11 PM
