Grep Options

Question 1

What does grep -i do?

Answer 1

Performs case-insensitive search, ignoring uppercase/lowercase differences
Example: grep -i “error” logfile.txt matches “Error”, “ERROR”, “error”
Essential for flexible pattern matching in logs and text files

Question 2

What is the purpose of grep -r or grep -R?

Answer 2

• Recursively searches through directories and subdirectories
• -r follows symbolic links, -R does not follow symbolic links
• Example: grep -r “function” /home/user/scripts/ searches all files in directory tree

Question 3

How does grep -n help with search results?

Answer 3

• Shows line numbers where matches are found
• Makes it easier to locate and edit specific lines in files
• Example: grep -n “TODO” *.py shows line numbers for each match

Question 4

What does grep -v accomplish?

Answer 4

• Inverts the search - shows lines that do NOT match the pattern
• Useful for filtering out unwanted content or debugging
• Example: grep -v “^#” config.file shows non-comment lines

Question 5

When would you use grep -l vs grep -L?

Answer 5

• -l lists only filenames that contain matches (not the matches themselves)
• -L lists filenames that do NOT contain matches
• Useful for finding which files contain or lack specific content

Question 6

What is grep -c used for?

Answer 6

• Counts the number of matching lines (not individual matches)
• Returns numeric count instead of showing actual matches
• Example: grep -c “error” /var/log/messages returns count of error lines

Question 7

How does grep -w differ from regular grep?

Answer 7

• Matches whole words only, not partial word matches
• Prevents false positives when searching for short terms
• Example: grep -w “cat” matches “cat” but not “catalog” or “concatenate”

Question 8

What does grep -A, grep -B, grep -C control?

Answer 8

• -A n shows n lines After each match
• -B n shows n lines Before each match
• -C n shows n lines of Context (both before and after)