This is the mail archive of the
mailing list for the Cygwin project.
Re: "run" changes behavior with cygwin-17.6
On Wed, 18 Aug 2010, Corinna Vinschen wrote:
> On Aug 18 15:22, Christopher Faylor wrote:
> > On Wed, Aug 18, 2010 at 03:19:06PM -0400, Christopher Faylor wrote:
> > >>already does for the environment. Dropping the environment had roughly
> > >>the same consequences way back when, after all.
> > >
> > >Except that not every program uses the windows environment. This affects
> > >quite a few native windows calls.
> It affects every program which calls CreateProcess or ShellExecute, for
> instance. This includes GDB, tcl, run, run2, cygstart, etc.
> > And, for that reason, I think we should reconsider this change. Maybe
> > as a compromise maybe we could at least avoid cd'ing to the dummy
> > location on entry to the first cygwin program.
> I disagree. When do you change the directory to //?/pipe then? The
> first time chdir is called?
Can someone please remind me why you shouldn't change to that directory
only when SetCurrentDirectory would fail due to a long path, virtual
path, etc? I think it was covered in the developer list, but I can't find
it right now.
Staff Realtime Software Engineer
VITAL - Visual Simulation Systems
the best safety device in any aircraft is a well-trained crew...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple