Author Topic: Build window weirdness with 'grep'  (Read 370 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1828
  • Hero Points: 177
  • Text
Build window weirdness with 'grep'
« on: October 04, 2018, 12:30:07 am »
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

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2369
  • Hero Points: 132
Re: Build window weirdness with 'grep'
« Reply #1 on: October 04, 2018, 12:02:58 pm »
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

  • Senior Community Member
  • Posts: 1828
  • Hero Points: 177
  • Text
Re: Build window weirdness with 'grep'
« Reply #2 on: October 04, 2018, 01:22:28 pm »
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

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1299
  • Hero Points: 130
Re: Build window weirdness with 'grep'
« Reply #3 on: October 04, 2018, 01:42:23 pm »
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.