Build window weirdness with 'grep'

[jporkkahtc]

I have cygwin "grep.exe" in my path.

In the Build window, if I type

Code: [Select]

D:\temp>
D:\temp>echo Before I hit Enter
Before I hit Enter

D:\temp>grep
Then when I hit <enter> on the GREP command, I get:

Code: [Select]

D:\temp>
D:\temp>echo Before I hit Enter
Before I hit Enter

D:\temp>echo VSLICKERRORPATH="D:\temp"
VSLICKERRORPATH="D:\temp"

D:\temp>grep
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.

D:\temp>


[Dan]

It's just the build that puts the error path in.  If you wanted to use the same path, you could write a script that put in VSLICKERRORPATH and then ran grep.  I'm not 100% sure if next-error and prev-error decide whether to look at VSLICKERRORPATH based on what regular expression is found.

[jporkkahtc]

But this only happens when I type "grep".
If I type "grep.exe" it doesn't.

So, slick must be special casing "grep" for some reason, even though I'm not using a slick built in command or anything.

This even happens when 'grep' isn't in my path.

[Lee]

There is a special case, def_error_info_commands has a space delimited list of executables where we may want to try to use next-error handler in the process buffer.