From: "Peter Dons Tychsen via cygwin" <cygwin@cygwin.com>
To: Ken Brown <kbrown@cornell.edu>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: execvp* and spawnvp* react differently to same PATH environment variable
Date: Wed, 09 Oct 2019 23:25:00 -0000 [thread overview]
Message-ID: <44c967db7f6941282c83a64ab4e966302379043a.camel@tdcadsl.dk> (raw)
In-Reply-To: <d613e3c2-0420-2233-2b1e-77c704824b3d@cornell.edu>
Hi Ken,
> I think you're probably right. The use of FE_NNF in execvp* was
> introduced in
> commit 6d63272b. I suspect it was just an oversight that the spawvp*
> functions
> weren't changed in the same way. I'll send a patch to the cygwin-
> patches list
> to fix this. When Corinna returns, she can tell us whether there's
> some reason
> that spawnvp should be different from execvp.
Excellent. Thanks for the fast response. I will keep an eye out for
when it lands.
Thanks,
/pedro
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-10-09 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 20:51 donpedro.tdcadsl.dk via cygwin
2019-10-09 16:43 ` Ken Brown
2019-10-09 23:25 ` Peter Dons Tychsen via cygwin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44c967db7f6941282c83a64ab4e966302379043a.camel@tdcadsl.dk \
--to=cygwin@cygwin.com \
--cc=donpedro@tdcadsl.dk \
--cc=kbrown@cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).