From: Dmitry Kakurin <dmitry.kakurin@gmail.com>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: msysgit: does git gui work?
Date: Fri, 10 Aug 2007 23:10:50 -0700 [thread overview]
Message-ID: <ACBC67D9E9124ECFAAF6B0E20CE660C0@ntdev.corp.microsoft.com> (raw)
In-Reply-To: <81b0412b0708100440l116f934ft22d3ac3c71e2e7cf@mail.gmail.com>
From: "Alex Riesen" <raa.lkml@gmail.com>
>> In my experience, Windows users (not Mac users forced to use Windows)
>> _expect_ "." to be in the PATH.
>
> ...because they _cannot_ know otherwise. In Windows, you cannot remove "."
> from PATH, it is implicitly in it.
> It is actually worse than that: the system directories are in PATH
> too. Unconditionally.
> Yes, the same system directories all them programs put their .exes into.
This is not true:
C:\>where cmd.exe
C:\Windows\System32\cmd.exe
C:\>set path=
C:\>cmd
'cmd' is not recognized as an internal or external command,
operable program or batch file.
Also there is an option to exclude implicit '.' from path, but no one uses it because too many things will break.
- Dmitry
next prev parent reply other threads:[~2007-08-11 6:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 7:24 msysgit: does git gui work? Steffen Prohaska
2007-08-09 21:23 ` Steffen Prohaska
2007-08-10 5:31 ` Shawn O. Pearce
2007-08-10 7:03 ` Steffen Prohaska
2007-08-10 7:38 ` Steffen Prohaska
2007-08-10 7:47 ` Marius Storm-Olsen
2007-08-10 10:26 ` Steffen Prohaska
2007-08-10 10:16 ` Johannes Schindelin
2007-08-10 10:51 ` Steffen Prohaska
2007-08-10 12:13 ` Johannes Schindelin
2007-08-10 13:48 ` Steffen Prohaska
2007-08-10 13:53 ` Johannes Schindelin
2007-08-10 16:47 ` Steffen Prohaska
2007-08-10 11:40 ` Alex Riesen
2007-08-11 6:10 ` Dmitry Kakurin [this message]
2007-08-11 8:40 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2007-08-10 22:00 Brett Schwarz
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=ACBC67D9E9124ECFAAF6B0E20CE660C0@ntdev.corp.microsoft.com \
--to=dmitry.kakurin@gmail.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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 NNTP newsgroup(s).