Question

1

rated 0 times [ 1] [ 0] / answers: 1 / hits: 763 / 2 Years ago, fri, november 11, 2022, 2:00:20

I cannot find the reason why grep cannot find the file with the word 'coomunities'. I used

grep -ril --include=GLOB "coomunities"  .

Note: communities is on purpose mispelled.
The file is a docx and currently has permissions '-rwxrwxrwx'. I tried

I tried the GUI of searchmonkey which can find the file correctly
still the file seems not appearing in any search using grep. Any idea?

Only authorized users can answer the question. Please sign in first, or register a free account.

Total Points: 220

Total Questions: 108

Total Answers: 105

Location: Serbia

Member since Fri, Jun 3, 2022

2 Years ago

hreadsoplet questions

Sat, Oct 9, 21, 17:57, 3 Years ago

Wed, May 25, 22, 18:11, 2 Years ago

Thu, Jan 20, 22, 09:26, 2 Years ago

Mon, Jan 24, 22, 20:23, 2 Years ago

Mon, Apr 17, 23, 18:22, 1 Year ago

answered 2 Years ago girdleas · Accepted Answer

Few issues.

You Can't grep a docx file. Grep works with standard output files or text. Docx is encoded
Take a look at this
How to search multiple DOCX files for a string within a Word field?
A quick way to verify this is to cat <file>.docx and see if what come out is readable or not.

Outside of the docx issue. I haven't used GLOB in grep, but my understanding is that it is pretty limited. Your better off using regex. Something like this

grep -Ei "coom[^[:space:]]+" *.<File Ext>

Personally when I can't find something I know should be there, I change the needle, not the haystack. Try "coom" or even "coo".

I don't think permission are the issue. Run the cat command, if you can read it then you don't need to change permission for grep.

Hope that helps.