[p4] Re: 'p4 have * ' under NT Cygwin bash

[Scott Blachowicz]

Scott Blachowicz <Scott.Blachowicz at seaslug.org> rambled:

> Your problem appears to be that normal behavior for a Unix-style shell is to
> expand filename wildcards before passing the args off to the sub-command. In
> this case your 'bash' is expanding the '*' to all the files in your directory,
> then passing the new arg list off to the p4 command.

Nevermind...I misread your original message (the above may be true,
but it also may be irrelevant :-)).  Sorry about that.

Mark Kohler <MKohler at Nomadix.com> wrote:

> I'm attempting to use the Perforce command-line client under Cygwin B20.1
> bash. The problem I have is that 'p4 have *' doesn't seem to work. It
> lists all the files in the local directory as not on client, even though
> some of them are.

In case it's relevant, I've gotten that kind of stuff when I use drive
substitutions...for example, if I have

	SUBST P: D:\Projects

I can cd to "P:\" and be in the same place on disk as cd'ing to
"D:\Projects", but the 'p4' command can't tell that they are the same
place.  So, if I get to the directory the wrong way, I can't do
anything with the p4 commands.

Also, some Unix-style shells set a PWD environment variable that, I
think, the p4 command line program pays attention to.  That cygwin
bash is probably setting it using it's own directory path notation and
mount table...and the p4 command isn't going to know what those paths
mean unless it's linked against the cygwin libraries...

Scott.Blachowicz at seaslug.org