[texworks] TeXworks 0.6.3 has problems with makeindex in a shell-scape situation

Claudio Beccari claudio.beccari at gmail.com
Sun May 5 19:19:30 CEST 2019

This is the configuration I have

----- configuration info -----
TeXworks version : 0.6.3r.a2470ca (travis-ci)
Install location : /Applications/TeXworks.app
Library path : /Users/claudio/Library/TeXworks/
pdfTeX location : /usr/local/texlive/2019/bin/x86_64-darwin/pdftex
Operating system : Mac OS X 10.14.4 (Darwin Kernel Version 18.5.0: Mon 
Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64)
Qt version : 5.12.1 (build) / 5.12.1 (runtime)

I upgraded to 0.6.3 before the release of TeX Live 2019, but I did not 
test it in a real deep way.
Now, as a moderator of the Italian Tex User Group Forum (www.guitex.org) 
I find a user who is trying to create an index throught the excellent 
package imakeidx.tex; he was successful with the previous version 0.6.2 
and of TeXLive 2018; Now with any of the three main typesetting engines 
pdfLaTeX, XeLaTeX and LuaLatex the index is not created any more. I 
tested his MWE:

% !TEX encoding = UTF-8 Unicode
% !TEX TS-program = lualatex










And verified that his claim was correct -- the absence of any font 
declaration and of language selection does not influence the behavior, 
at the same time it allow to try typesetting the MWE with any of the 
three main engines.

Apprently it fails also running the compilation throug the command line.

On the opposite if you tyoeset thet MWE through TeXShop everything goes 
as expected and the index is created normally.

I suspect the it depends on some command line option the is missing.  Of 
course the options in TeXworks are specified therugh the Preferences 
menu entry Typesetting where the command line list of names and options 
is preset upon installing.
Running the requested typesetting throug the command line does not 
change the situation, because the user does not know the misterious 
requested missing option.

The fact the TeXworks 0.6.2 works as expected even with TeX Live 2019, 
excludes that the cause ot this behavior is in the TeX Live engines. Or 
at least that, even if something is changed in TL2019 with respect to 
TL2018, it had no influence on TeXworks 0.6.2, but it does on TeXworsk 

I tested this behavior with some of my real documents, non MWE, and the 
situation did not change.

Since I always suggest using the the forum frequenters the USE of 
TeXworks, I wish this strange bug is corrected as soon as possible; but 
this depends only on you because, for my dismay, I cannot give you more 
clues than what I did above, and my be my suspects are oriented in the 
wrong direction.

Thank you very much


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/texworks/attachments/20190505/33d8d96b/attachment.html>

More information about the texworks mailing list