TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I always forget the syntax of command-line tools for searching through multiple files. What's the easiest/fastest way to search through, say, all of the .sty files distributed in TeX Live for the occurrence of a string, say, \everypar? (Let's assume Linux/Mac OS X.)

share|improve this question
hmmm. off topic? – Yossi Farjoun Oct 13 '10 at 14:48
This isn't really a TeX related question. But find is your friend here. – Juan A. Navarro Oct 13 '10 at 14:50
This would be answered in 5 seconds flat over at stackoverflow... – Yossi Farjoun Oct 13 '10 at 14:55
I'm certainly not going to argue that this doesn't toe the line of being off-topic. But it's a tool I'd like to have in my belt for LaTeX development, so I figured I'd see if anyone's done this before. – Will Robertson Oct 13 '10 at 14:56
You don't need find. Just grep -r --include=*.sty "\\everypar" <DIR> (Need to escape the backslash.) – Willie Wong Oct 13 '10 at 15:28
up vote 9 down vote accepted

I'm using a script called texgrep like this:

texgrep everypar sty

backslashes should be quoted. Here's the source of the script:

Search pattern:

# texgrep - searches for a text pattern contained in files
#   located inside the texmf trees
# usage: texgrep pattern [extension]
# usage examples:
#   texgrep phantomsection sty
#   texgrep \\\\def\\\\phantomsection
if [ $# -eq 0 ]; then
  echo 1>&2 Usage: texgrep pattern [extension]
  exit 1
 find `kpsewhich --var-value=$path` -type f -name "*$2" |xargs grep $1
exit 0

It's valuable for me because I like to read sources and this saves me time. I've put the script on my blog some time ago: Speed up the work by shell scripts.

More scripts related to search & work:

Search and edit:

# texedit - find one or several tex related files
#   and open them in the editor
if [ $# -eq 0 ]; then
  echo 1>&2 Usage: texedit file1 [file2] ...
  exit 1
gedit `kpsewhich $@`
exit 0

Search and look around:

# texls - list the content of the directory
#   corresponding to a certain tex related file
if [ $# -eq 0 ]; then
  echo 1>&2 Usage:    texls filename [pattern]
  echo 1>&2 examples: texls babel.sty
  echo 1>&2           texls book.cls *clo
  exit 1
ls `kpsewhich $1 | sed 's/\(.*\)\/.*$/\1\//'`$2
exit 0

Search and change to directory:

# texcd - change into the directory
#   corresponding to a certain tex related file
if [ $# -eq 0 ]; then
  echo 1>&2 Usage:    . texcd filename [pattern]
  echo 1>&2 examples: . texcd beamer.cls
  exit 1
cd `kpsewhich $1 | sed 's/\(.*\)\/.*$/\1/'`
echo Changed to: `pwd`

All could be done by shell functions instead of scripts. Like Michael suggested in my blog:

function texcd ()
cd $(dirname "$(kpsewhich "$1")");

I hope it's useful for somebody, even though it goes beyond the question.

share|improve this answer
These are great! Briefly trying Willie's suggestion to use grep instead of find seems to show a significant speedup, if you're interested. – Will Robertson Oct 14 '10 at 7:50

This is what I do:

ack --tex '\\everypar' /opt/texlive2010

has really nice output (and a TextMate bundle as well - but that's not the question) and is quite fast. Make sure you've got everything you need in the --tex part by setting in the ~/.ackrc or on the command line something like this:


(you should also include .mkiv and .mkii, you know ;-))

share|improve this answer
I forgot: ack is a replacement for grep -r. See the ack homepage for more info. – topskip Oct 13 '10 at 18:10
A speed comparison of different grep alternatives – Aditya Oct 13 '10 at 19:31
Never seen such a crappy comparison. – topskip Oct 13 '10 at 20:26

Well, my command lines tend to be quite verbose, but I think you could search for all occurances of foo in sty files on $TEXMF by:

for texmf in `kpsewhich -expand-path '$TEXMF' | sed 's/:/ /g'`; do 
  find $texmf | grep '\.sty$' | xargs -J% grep -n 'foo' %; 

Now that I've had my morning vat o' coffee (and read some comments), a more concise version would be:

grep -r --include=*.sty -n '\\everypar' `kpsewhich -expand-path '$TEXMF' | sed 's/:/ /g'`
share|improve this answer

It is slightly easier for ConTeXt. Just enter your search phrase in the search box here

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.