I was once trying to run a grep command to a directory and looking for a string inside it.
While the directory I was looking into was in a different drive (F:) than that of the system drive (C:) where the grep was installed.

I used the command prompt to first descend into the directory. So, I first went into the directory such that my command prompt looked like as follows:
    F:\MySearchDirectory>

As I was already into this directory, I just shot the gremp command like the following:

    grep -r "mysearchstring"

But this came with an error as follows:

    grep: (standard input): Not enough space

Of course my computer did not have any issues with the space as this was an I7 processor with a huge 16GB of RAM and the hard disk had more than 40% available in all the drives.

This must have to be something else.

I tried to find out but the solutions given were rather too geeky like installing cygwin to do this.

However, I tried to do this using another method. I closed the command prompt and started it again. I did not change my directory in the commmand prompt to F: drive this time. Rather I just shot the following command at its default location:

    grep -r "mysearchstring" F:\MySearchDirectory

And lo, the result was out there in no time.

So, what did it do? I guess wingrep works best when it is in its default location and target anything at other location.

Hope this helps another Windows user.

 

Add comment


Security code
Refresh