Grep error binary file standard input matches

Also see: How does -a command line option in grep work? Improve this answer. Olorin Olorin 3, 14 14 silver badges 27 27 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. When the function has special characters, this plugin will show up this error information output by grep , this error was shown on every executed command, here is the key code line caused the error, it could be easily reproduced by using zsh-vi-mode at the same time.

The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. How is it possible that egrep sees piped data from functions as binary? Does the zsh-vi-mode overload functions? None of the functions declared in the plug-in seem have non-ascii characters. Binary file standard input matches when grepping tail. Published October 21st, If TYPE is without-match, grep assumes that a binary file does not match; this is equivalent to the -I option.

If TYPE is text, grep processes a binary file as if it were text; this is equivalent to the -a option. Add -a switch to grep to make it treat the file a readable text. Most probably your input files contain some unreadable characters. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Diff command along with Grep gives "Binary file standard input matches" Ask Question. Asked 2 years, 5 months ago.

Active 2 years, 5 months ago. Viewed 6k times. I am using the below command to put my required output to the file 'diff.