tags:

views:

6

answers:

0
Q: 

grep in gvim always returns E40: Can't open errorfile

I am using gvim grep that defaults to findstr in a Windows XP environment. The gvim has access to the folder where the error file is to be opened, but it fails. Is there anyway to change where the error file goes? Do you have any other tips/suggestions for using findstr in gvim for windows?

related questions

What is makeinfo, and how do I get it?
Efficient grep method to match two atoms?
Useful Regular Expression Tutorial
How can I extract lines of text from a file?
Groovy grep a word
Regex in awk and WinGrep
Shell script to find bigrams.
Make a Perl-style regex interpreter behave like a basic or extended regex interpreter
grep --exclude/--include syntax (do not grep through certain files)
Fast recursive grepping of svn working copy
Quick unix command to display specific lines in the middle of a file?
grep: matching on literal "+"
What's the best way to find a string/regex match in files recursively? (UNIX)
Deleting multiline text from multiple files
How to do something with bash when a text line appear to a file
How can I write a shell script to direct grep data into a date-based filename?
Colored grep?
Count number of occurences of token in a file
Use grep to find content in files and move them if they match
What are good grep tool for Windows?
how do you search for files containing dos line endings (CRLF) with grep under linux?
Regex to match unique substrings
How do I find broken NMEA log sentences with grep?
Summary of differences in Regular Expression syntax for various tools and languages?
grep a file, but show several surrounding lines?