grep

If you actually needs a particular shell's local history, pipe grep through a grep for the PID (I find I almost never need that).

C works way better with established tools like grep and co, as it does not do function overloading.

FOO=~/bin/vim export FOO env | grep FOO shows it as expanded.

Possibly my grep was also better at checking variant field names?

Similarly, I can comfortably switch from Linux to OS X to FreeBSD thanks to bash and the gazillion posix tools (grep, ps, awk...).

Sorry, I was just really curious how you grep/awk/sed through some man pages.

#!/bin/sh if grep --quiet '<?php' $1; then echo 'run for your lives!' else echo 'phew.

(If not, that would explain it) Do you claim the same thing for all the other gnu tools (grep et al)?

Armed with the arcane power of ancient spaghetti code shell scripts and logical fallacies, they grep their way through enemy lines to banish the dreaded modernity once and for all.

Just set up a PC as Wifi hotspot with the same name as the target network and grep the credentials from the devices that try to automatically connect to your PC.

In a lot of cases it's because people prefer to keep things DRY, but it hurts when you're trying to grep through a large codebase to find that one method you need.

Same here, I get: oathkeeper:~ user$ security find-generic-password -ga labnol | grep password security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.

Use "grep -R" to find every single invocation you ever made to that program.

%[sh -c '#{results.join(" | ")}'] ~ I've tried a few things but keep getting this: Running: sh -c 'grep -e hello access.log' This application has requested the Runtime to terminate it in an unusual way.

Grep for all arithmetic in your choice of program and the vast, vast majority are not deliberately using overflow behavior for some effect.