On Sun, Feb 12, 2006 at 12:26:22PM -0800, Yitzchak Scott-Thoennes wrote:
>On Sun, Feb 12, 2006 at 11:57:00AM -0500, Christopher Faylor wrote:
>>If we don't get a single person indicating that they rely on the
>>current behavior then I'm ok with changing it. We have a patch ready
>>to be checked in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Faylor on 2/12/2006 9:57 AM:
>
> I don't mind protecting people against the evil 3PP which corrupt the
> PATH but, as I said, since we don't get that many complaints about the
> current behavior (which may actually have been i
On 10 February 2006 19:01, Corinna Vinschen wrote:
> On Feb 8 18:59, Dave Korn wrote:
>>
>> Since POSIX semantics requires an empty path component to be treated as
>> $CWD, but Win32 semantics require an empty path component to be ignored,
> ^
On Sun, Feb 12, 2006 at 11:57:00AM -0500, Christopher Faylor wrote:
> If we don't get a single person indicating that they rely on the current
> behavior then I'm ok with changing it. We have a patch ready to be
> checked in, in fact.
I assume that:
$ PATH="/foo::$PATH" cmd /c printenv PATH
On Sun, Feb 12, 2006 at 01:03:18PM +0100, Corinna Vinschen wrote:
>On Feb 11 20:22, Eric Blake wrote:
>>I strongly oppose option 3 - cygwin should never add '.' implicitly to
>>the front of a POSIX path - if you are crazy enough to want dot there,
>>put it there yourself explicitly. But I like opt
On Feb 12 13:52, John Morrison wrote:
> On Sun, February 12, 2006 11:58 am, Corinna Vinschen wrote:
> > On Feb 12 08:44, John Morrison wrote:
> >> Would a reasonable solution would be to make the PATH environment
> >> variable
> >> a special case and parse it when set? (Appologies if this isn't a
On Sun, February 12, 2006 11:58 am, Corinna Vinschen wrote:
> On Feb 12 08:44, John Morrison wrote:
>> On Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote:
>> > We're
>> > just trying go figure out if removing the ;; translation will affect
>> > many people. We're not looking to add things
On Feb 11 20:22, Eric Blake wrote:
> I strongly oppose option 3 - cygwin should never add '.' implicitly to the
> front of a POSIX path - if you are crazy enough to want dot there, put
> it there yourself explicitly. But I like option 2, of squeezing ';;' into a
> single ':' (avoiding the implicit
On Feb 12 08:44, John Morrison wrote:
> On Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote:
> > We're
> > just trying go figure out if removing the ;; translation will affect
> > many people. We're not looking to add things to the PATH.
> >
> > There is a tradeoff here and I don't believe
On Feb 11 15:24, Stephan Mueller wrote:
> cgf wrote:
> " So, I don't think this really answers Corinna's question. I believe that
> " she was looking for documentation which stated that ;; was ignored, not
> " reasoning which implies it.
>
> In the absence of the former, I'd hope the latter would
On Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote:
> We're
> just trying go figure out if removing the ;; translation will affect
> many people. We're not looking to add things to the PATH.
>
> There is a tradeoff here and I don't believe that we really know what
> the implications are.
cgf wrote:
" On Sat, Feb 11, 2006 at 12:02:47PM -0800, Stephan Mueller wrote:
" >On Friday, Feb 10, Corinna wrote:
" >" On Feb 8 18:59, Dave Korn wrote:
" >" > On 08 February 2006 13:06, Eric Blake wrote:
" >" > > Yes, this is correct behavior, but it often catches people by surprise.
" >" > > POS
Eric writes:
" " > " There are two different points of view possible here:
" > "
" > " - Changing an empty Win32 path component to a POSIX "." entry is in
" > " Cygwin for a long time. It's possible that people rely on this
" > " behaviour, so changing it would break existing installations.
"
On Sat, Feb 11, 2006 at 12:02:47PM -0800, Stephan Mueller wrote:
>On Friday, Feb 10, Corinna wrote:
>" On Feb 8 18:59, Dave Korn wrote:
>" > On 08 February 2006 13:06, Eric Blake wrote:
>" > > Yes, this is correct behavior, but it often catches people by surprise.
>" > > POSIX requires an empty st
>
> " There are two different points of view possible here:
> "
> " - Changing an empty Win32 path component to a POSIX "." entry is in
> " Cygwin for a long time. It's possible that people rely on this
> " behaviour, so changing it would break existing installations.
> " Removing "." from
On Friday, Feb 10, Corinna wrote:
" On Feb 8 18:59, Dave Korn wrote:
" > On 08 February 2006 13:06, Eric Blake wrote:
" > > Yes, this is correct behavior, but it often catches people by surprise.
" > > POSIX requires an empty string in your PATH to be treated as the current
" > > directory, and wh
On Feb 8 18:59, Dave Korn wrote:
> On 08 February 2006 13:06, Eric Blake wrote:
> > Yes, this is correct behavior, but it often catches people by surprise.
> > POSIX requires an empty string in your PATH to be treated as the current
> > directory, and while people are less likely to start their Wi
On 08 February 2006 13:06, Eric Blake wrote:
PATH is "inherited" from my WinXP environment as usual but it is not
prepend with "/bin" like before the upgrade, and is now appended with
".".
> According to Julien Thewys on 2/8/2006 2:58 AM:
>> Solution is to reinstall 'base-files' (s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ugh - top-posting reformatted. http://cygwin.com/acronyms/#TOFU
>
> On 2/6/06, Eric Blake wrote:
Ugh - http://cygwin.com/acronyms/#PCYMTNQREAIYR
>>>PATH is "inherited" from my WinXP environment as usual but it
Solution is to reinstall 'base-files' (see
http://www.cygwin.com/ml/cygwin/2006-02/msg00222.html).
My PATH was appended with '.' because of a trailing ';' in my Windows PATH.
Thank you.
--
jt
On 2/6/06, Eric Blake <[EMAIL PROTECTED]> wrote:
> > I upgrade to 1.5.19-4 and my default PATH has chang
> Try opening a cmd.com window in c:\cygwin\bin (or whatever it is
> named), then running 'bash --login -xv' to see every command executed
> by bash during startup. Maybe that will help you pinpoint the
> culprit.
This really helps understand why it takes so long to open a bash shell,
the login
> I upgrade to 1.5.19-4 and my default PATH has changed:
>
> PATH is "inherited" from my WinXP environment as usual but it is not
> prepend with "/bin" like before the upgrade, and is now appended with
> ".".
> I cannot find where this happen (my .bashrc is unchanged).
Try opening a cmd.com windo
22 matches
Mail list logo
