[OS X TeX] making an index (nomenclature)
Nicolae Garleanu
nbgarleanu at gmail.com
Mon Feb 5 18:24:40 EST 2024
I don’t mean to try to have anyone else waste time on this, but just in case it rings a bell with anyone: On my “real” file,
1. If I run makeindex from command line all OK.
2. The % !TEX program = pdflatexmk snippet at the top of the file does not do anything. It does work on the MWE.
The two files are in the same directory. All the nomenclature related commands in the MWE are also in the real file.Is there a way to run pdflatexmk from the command line as a check? Just writing it followed by file name gives me a “command not found" error (as it perhaps should).
Nicolae
> On Feb 5, 2024, at 16:50, Nicolae Garleanu <nbgarleanu at gmail.com> wrote:
>
> I figured out that I had to move the pdflatexmk engine from “Inactive” to the Engines folder. My simple example now works. (The real file I want to use it on does not, but the problem must be of a different nature.) Thanks again.
> Nicolae
>
>
>
>> On Feb 5, 2024, at 14:48, John Collins <jcc8 at psu.edu> wrote:
>>
>> 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:
>>
>> makeindex ⟨filename⟩.nlo -s nomencl.ist -o ⟨filename⟩.nls
>>
>> 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.
>>
>> John Collins
>>
>>
>> On 2/5/24 3:18 PM, Herbert Schulz via MacOSX-TeX wrote:
>>>> On Feb 5, 2024, at 1:09 PM, Nicolae Garleanu <nbgarleanu at gmail.com>
>>>> wrote:
>>>> Hi Herb,
>>>> Yes, I think it is pdflatex, although I do not remember (I think I used to
>>>> know, at least) why in the Typeset menu Pdftex is checked (as is LaTeX).
>>>> More important, I put % !TEX program = pdflatexmk as the first line of the
>>>> document (I tried both before and after \document class — I used the
>>>> syntax %TEX root = …, after \documentclass, with success in other files).
>>>> As before, no new file other than the .nlo, but no error on executing.
>>>> I haven’t tried the terminal, but I wonder whether that is the most
>>>> efficient way to uncover the problem. I had a quick look over the .log
>>>> file for anything that would catch my eye, and did see "No file
>>>> Try-nomencl.nls,” which didn’t surprise me, but I don’t know why this file
>>>> failed to be produced. Maybe I should also say that I never did anything
>>>> actively to set up pdflatexmk. Were it not for Overleaf, I would keep
>>>> thinking that I have a syntax error vis-a-vis the nomenclature package.
>>>> Nicolae
>>> Howdy,
>>> How did you typeset the file? Did you use Typeset->Typeset (Cmd-T)?
>>> I usually put it at the top of the file but within the first 20 lines of the
>>> file is OK too.
>>> When I typeset using the pdflatexmk engine it all automatically gets
>>> compiled (no need for separate runs of pdflatex, makeindex, pdflatex the
>>> engine takes care of everything and teXShop configures things so that the
>>> engine knows how to deal with .nlo files, etc. I get a fully typeset file
>>> with the nomenclature there.
>> ----------- Please Consult the Following Before Posting -----------
>> TeX FAQ: https://www.tug.org/mactex/faq/index.html
>> List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/TeX/
>> List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
>> https://email.esm.psu.edu/pipermail/macosx-tex/
>> TeX on Mac OS X Website: https://www.tug.org/mactex/index.html
>> List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex
>
More information about the MacOSX-TeX
mailing list