I used \makeglossaries in the preamble. Defined my terms, and issued \printglossaries. I've been reading the manual but can't see what I'm missing:



description={(1) The rate of flow of metabolites through a metabolic pathway.  (2) The rate of transport per unit of area.}}




Edit: it is true I don't actually use the glossary terms in the text body - this is purely a stand-alone glossary.

2 Answers 2


An actual answer this time:

Use makeglossaries <bare filename> and then recompile the document, and all should be well.

My understanding is that you must compile the document first, since this is what generates the files makeglossaries acts on.

  • Is this supposed to be performed on the .tex file which includes your glossary, or on the .glo file itself? Do I include this in the preamble, or is this to happen inside windows commandline terminal? Thanks.
    – ptrcao
    Jun 17, 2011 at 3:12
  • 1
    When glossaries was installed, you should have gained a command (a Perl script, specifically) called makeglossaries. Say your file is called glossary.tex. You would cd to the directory where it is and run makeglossaries glossary. Then it'll handle the rest and you can recompile your document. See my edit above. Jun 17, 2011 at 3:16
  • Is this a one-time requirement or do I have to makeglossaries everytime I add new terms to the glossary? The way it's set up seems a bit inconvenient, I'd rather not have to go thru this process in terminal everytime... :|
    – ptrcao
    Jun 17, 2011 at 3:23
  • 1
    You could always write a script to automate the process. As far as I can tell from the docs, this is the way it has to be done. For instance, if you keep all your glossary files in one directory, you can make a simple batch file to cd to that directory and run makeglossaries on the file you want (or on all of them). Jun 17, 2011 at 3:31
  • 1
    Other then the deprecated glossary package, I can't think of any. The LaTeX Wikibook section on glossaries may be informative, though. Unfortunately, there doesn't appear to be a way around using the command line a little unless you're willing to do a little bit of scripting now. Alternatively, you need not recompile your glossary every time you add a new entry. Just do so periodically to check for errors. When you're ready to finish the glossary, run makeglossaries and you're done. That saves you the trouble of using the command line often. Jun 17, 2011 at 4:00

Have you used makeglossaries, xindy or makeindex, yet? This section suggests that you need to use one of them before the entries will print.

CW'd since it's really more of a comment than an answer.

EDIT: I've just tried that, and that's the way. Just run makeglossaries <name of file> and it'll work. Don't use any extension, though. Just the bare name of your file. Note non-CW answer now active.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .