Can I have TeXworks run my command line argument?












0














I am using a solution to an issue I am having with generating a glossary found here:



List of glossaries not displaying



As part of the solution, Christian Hupfer suggests compiling with the following command pipeline



pdflatex foo

makeindex -s foo.ist -o foo.gls foo.glo

pdflatex foo


I noticed that when I am trying to compile in TeXworks using the pdfLaTeX + makeindex + bibtex command, that it fails to generate the glossary because it is missing the foo.ist, foo.gls, foo.gls files.



To solve this, I simply wrote a one line batch file:



makeindex -s workingpaper.ist -o workingpaper.gls workingpaper.glo


which I run prior to compiling my document with the aforementioned pdfLaTeX + makeindex + bibtex option.



However, looking through the TeXworks preferences under typesetting options, I get the sense that I don't need the batch file at all and I can set TeXworks to do it for me without the need to rewrite the batch file for every paper I have that I intend to include a glossary (i.e., substituting "foo" with the appropriate file name).



I've tried editing some of the existing processing tools in the preference menu to get an idea of how I might do this, but the syntax is sufficiently foreign to me that I am completely lost.



I am running MikTeX 2.9 incase this is helpful information.










share|improve this question






















  • You can also use the makeglossaries script. Since I am Linux user by 'birth' I am accustomed to use command line in order to get my work done. I see that Windows user are 'forced' to use such 'tools' like TexWorks, however. I believe, that those tools often use %f or similar in the tools configuration dialogs in order to indicate the name of the .tex file
    – Christian Hupfer
    12 mins ago












  • The pdflatex+makeindex+bibtex command uses texify and passing options to it is imho quite a pain. Better create a new tool in the preferences that calls makeglossaries and pass the file name with $basename.
    – Ulrike Fischer
    5 mins ago
















0














I am using a solution to an issue I am having with generating a glossary found here:



List of glossaries not displaying



As part of the solution, Christian Hupfer suggests compiling with the following command pipeline



pdflatex foo

makeindex -s foo.ist -o foo.gls foo.glo

pdflatex foo


I noticed that when I am trying to compile in TeXworks using the pdfLaTeX + makeindex + bibtex command, that it fails to generate the glossary because it is missing the foo.ist, foo.gls, foo.gls files.



To solve this, I simply wrote a one line batch file:



makeindex -s workingpaper.ist -o workingpaper.gls workingpaper.glo


which I run prior to compiling my document with the aforementioned pdfLaTeX + makeindex + bibtex option.



However, looking through the TeXworks preferences under typesetting options, I get the sense that I don't need the batch file at all and I can set TeXworks to do it for me without the need to rewrite the batch file for every paper I have that I intend to include a glossary (i.e., substituting "foo" with the appropriate file name).



I've tried editing some of the existing processing tools in the preference menu to get an idea of how I might do this, but the syntax is sufficiently foreign to me that I am completely lost.



I am running MikTeX 2.9 incase this is helpful information.










share|improve this question






















  • You can also use the makeglossaries script. Since I am Linux user by 'birth' I am accustomed to use command line in order to get my work done. I see that Windows user are 'forced' to use such 'tools' like TexWorks, however. I believe, that those tools often use %f or similar in the tools configuration dialogs in order to indicate the name of the .tex file
    – Christian Hupfer
    12 mins ago












  • The pdflatex+makeindex+bibtex command uses texify and passing options to it is imho quite a pain. Better create a new tool in the preferences that calls makeglossaries and pass the file name with $basename.
    – Ulrike Fischer
    5 mins ago














0












0








0







I am using a solution to an issue I am having with generating a glossary found here:



List of glossaries not displaying



As part of the solution, Christian Hupfer suggests compiling with the following command pipeline



pdflatex foo

makeindex -s foo.ist -o foo.gls foo.glo

pdflatex foo


I noticed that when I am trying to compile in TeXworks using the pdfLaTeX + makeindex + bibtex command, that it fails to generate the glossary because it is missing the foo.ist, foo.gls, foo.gls files.



To solve this, I simply wrote a one line batch file:



makeindex -s workingpaper.ist -o workingpaper.gls workingpaper.glo


which I run prior to compiling my document with the aforementioned pdfLaTeX + makeindex + bibtex option.



However, looking through the TeXworks preferences under typesetting options, I get the sense that I don't need the batch file at all and I can set TeXworks to do it for me without the need to rewrite the batch file for every paper I have that I intend to include a glossary (i.e., substituting "foo" with the appropriate file name).



I've tried editing some of the existing processing tools in the preference menu to get an idea of how I might do this, but the syntax is sufficiently foreign to me that I am completely lost.



I am running MikTeX 2.9 incase this is helpful information.










share|improve this question













I am using a solution to an issue I am having with generating a glossary found here:



List of glossaries not displaying



As part of the solution, Christian Hupfer suggests compiling with the following command pipeline



pdflatex foo

makeindex -s foo.ist -o foo.gls foo.glo

pdflatex foo


I noticed that when I am trying to compile in TeXworks using the pdfLaTeX + makeindex + bibtex command, that it fails to generate the glossary because it is missing the foo.ist, foo.gls, foo.gls files.



To solve this, I simply wrote a one line batch file:



makeindex -s workingpaper.ist -o workingpaper.gls workingpaper.glo


which I run prior to compiling my document with the aforementioned pdfLaTeX + makeindex + bibtex option.



However, looking through the TeXworks preferences under typesetting options, I get the sense that I don't need the batch file at all and I can set TeXworks to do it for me without the need to rewrite the batch file for every paper I have that I intend to include a glossary (i.e., substituting "foo" with the appropriate file name).



I've tried editing some of the existing processing tools in the preference menu to get an idea of how I might do this, but the syntax is sufficiently foreign to me that I am completely lost.



I am running MikTeX 2.9 incase this is helpful information.







texworks






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 25 mins ago









Echan

26128




26128












  • You can also use the makeglossaries script. Since I am Linux user by 'birth' I am accustomed to use command line in order to get my work done. I see that Windows user are 'forced' to use such 'tools' like TexWorks, however. I believe, that those tools often use %f or similar in the tools configuration dialogs in order to indicate the name of the .tex file
    – Christian Hupfer
    12 mins ago












  • The pdflatex+makeindex+bibtex command uses texify and passing options to it is imho quite a pain. Better create a new tool in the preferences that calls makeglossaries and pass the file name with $basename.
    – Ulrike Fischer
    5 mins ago


















  • You can also use the makeglossaries script. Since I am Linux user by 'birth' I am accustomed to use command line in order to get my work done. I see that Windows user are 'forced' to use such 'tools' like TexWorks, however. I believe, that those tools often use %f or similar in the tools configuration dialogs in order to indicate the name of the .tex file
    – Christian Hupfer
    12 mins ago












  • The pdflatex+makeindex+bibtex command uses texify and passing options to it is imho quite a pain. Better create a new tool in the preferences that calls makeglossaries and pass the file name with $basename.
    – Ulrike Fischer
    5 mins ago
















You can also use the makeglossaries script. Since I am Linux user by 'birth' I am accustomed to use command line in order to get my work done. I see that Windows user are 'forced' to use such 'tools' like TexWorks, however. I believe, that those tools often use %f or similar in the tools configuration dialogs in order to indicate the name of the .tex file
– Christian Hupfer
12 mins ago






You can also use the makeglossaries script. Since I am Linux user by 'birth' I am accustomed to use command line in order to get my work done. I see that Windows user are 'forced' to use such 'tools' like TexWorks, however. I believe, that those tools often use %f or similar in the tools configuration dialogs in order to indicate the name of the .tex file
– Christian Hupfer
12 mins ago














The pdflatex+makeindex+bibtex command uses texify and passing options to it is imho quite a pain. Better create a new tool in the preferences that calls makeglossaries and pass the file name with $basename.
– Ulrike Fischer
5 mins ago




The pdflatex+makeindex+bibtex command uses texify and passing options to it is imho quite a pain. Better create a new tool in the preferences that calls makeglossaries and pass the file name with $basename.
– Ulrike Fischer
5 mins ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f467928%2fcan-i-have-texworks-run-my-command-line-argument%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f467928%2fcan-i-have-texworks-run-my-command-line-argument%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Futebolista

F# list compare

Jornalista