The point of LaTeXing not being FLOSS is truly important and betting for small-scale closed-source is always risky. If the software author pulls the plug, forking by others is often not an option.
... And as it happens, look what is now WAS figuring prominently on the LaTeXing home page:
2014-06-27 16:48 by Chris
The purchase of a license for LaTeXing is temporary not possible. Due
to personal issues the distribution is stopped and will be not
continued for a few month. This is not the end of LaTeXing, the
program will still receive updates and bug fixes during that time.
As of March 2020, the LaTeXing github repository has been inactive since 2015 (except for one typo in a 2018 pull request). One fork has some extra snippets added, otherwise all forks are inactive.
There are a few different ways this could be approached.
The traditional
builder that LaTeXTools uses launches latexmk
, so you can solve the issue the same way you would for latexmk
, i.e., add a .latexmkrc
file to the directory containing your main tex document with the following contents:
add_cus_dep('glo', 'gls', 0, 'makeglossaries');
add_cus_dep('acn', 'acr', 0, 'makeglossaries');
sub makeglossaries {
if ($silent) {
system("makeglossaries -q \"$_[0]\"");
} else{
system("makeglossaries \"$_[0]\"");
}
}
push @generated_exts, 'glo', 'gls', 'glg';
push @generated_exts, 'acn', 'acr', 'alg';
$clean_ext .= ' %R.ist %R.xdy';
I've based this on both the latexmk
example file and this answer to a similar question.
Alternatively, as suggested in this question (I assume this is the one you were referring to), is to use the script
builder. To do this, in your LaTeXTools.sublime-settings
file (or, better, in the settings
section of your Sublime project file, you need to change the builder
setting to script
and then change the builder_settings
block to something like this:
"builder_settings": {
"osx": {
"script_commands": [
"pdflatex -interaction=nonstopmode -synctex=1",
"makeglossaries",
"pdflatex -interaction=nonstopmode -synctex=1",
"pdflatex -interaction=nonstopmode -synctex=1"
]
}
}
Personally, I'd choose the former of these, as the second option will run the whole script every time you build, which could take an unnecessary amount of time if you're working on a really long document.
Best Answer
It would be best to update your Perl installation, since it appears to be several years outdated. (The release date of version 2.08 of the
File::Path
module is 2009-10-04; this is the minimum version thatlatexmk
tests for.)However, you could try changing the
latexmk.pl
file to change the lineto
If that gives you no trouble, you are OK.
(Perhaps some experts on
Perl
and its history could suggest whether the version test that I wrote into thelatexmk
code is too conservative.)