<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Thanks, John and Herb.<div><br></div><div>I ran the makeindex command from the terminal prompt, and then got the pdf output expected. I conclude that neither makeindex, nor latexmk — which I used exactly as detailed by Herb — work for me. As I said, I never did anything specific to set them up, but I also didn’t know — even now I don’t know — that I had to. </div><div><br></div><div>Is there a quick way to find out how to set these up?</div><div><br id="lineBreakAtBeginningOfMessage"><div>
<div>Nicolae</div><div><br></div><br class="Apple-interchange-newline">
</div>
<div><br><blockquote type="cite"><div>On Feb 5, 2024, at 14:48, John Collins <jcc8@psu.edu> wrote:</div><br class="Apple-interchange-newline"><div><div>It's worth adding that to make the kind of index used by the nomenclature package, the command line to invoke makeindex is not the one for a standard index, but a modified one. Here's what the documentation for the nomencl package says to do:<br><br> makeindex ⟨filename⟩.nlo -s nomencl.ist -o ⟨filename⟩.nls<br><br>As Herb explained, the pdflatexmk engine in TeXShop (and its xelatexmk etc relatives) provide a special configuration to latexmk to get makeindex invoked appropriately for the nomenclature.<br><br>John Collins<br><br><br>On 2/5/24 3:18 PM, Herbert Schulz via MacOSX-TeX wrote:<br><blockquote type="cite"><blockquote type="cite">On Feb 5, 2024, at 1:09 PM, Nicolae Garleanu <nbgarleanu@gmail.com><br>wrote:<br>Hi Herb,<br>Yes, I think it is pdflatex, although I do not remember (I think I used to<br>know, at least) why in the Typeset menu Pdftex is checked (as is LaTeX).<br>More important, I put % !TEX program = pdflatexmk as the first line of the<br>document (I tried both before and after \document class — I used the<br>syntax %TEX root = …, after \documentclass, with success in other files).<br>As before, no new file other than the .nlo, but no error on executing.<br>I haven’t tried the terminal, but I wonder whether that is the most<br>efficient way to uncover the problem. I had a quick look over the .log<br>file for anything that would catch my eye, and did see "No file<br>Try-nomencl.nls,” which didn’t surprise me, but I don’t know why this file<br>failed to be produced. Maybe I should also say that I never did anything<br>actively to set up pdflatexmk. Were it not for Overleaf, I would keep<br>thinking that I have a syntax error vis-a-vis the nomenclature package.<br>Nicolae<br></blockquote>Howdy,<br>How did you typeset the file? Did you use Typeset->Typeset (Cmd-T)?<br>I usually put it at the top of the file but within the first 20 lines of the<br>file is OK too.<br>When I typeset using the pdflatexmk engine it all automatically gets<br>compiled (no need for separate runs of pdflatex, makeindex, pdflatex the<br>engine takes care of everything and teXShop configures things so that the<br>engine knows how to deal with .nlo files, etc. I get a fully typeset file<br>with the nomenclature there.<br></blockquote>----------- Please Consult the Following Before Posting -----------<br>TeX FAQ: https://www.tug.org/mactex/faq/index.html<br>List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/TeX/<br>List Archives: http://dir.gmane.org/gmane.comp.tex.macosx<br> https://email.esm.psu.edu/pipermail/macosx-tex/<br>TeX on Mac OS X Website: https://www.tug.org/mactex/index.html<br>List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex<br></div></div></blockquote></div><br></div></body></html>