Configuring `TeXMaker` to work with the `TeXLive` distribution












2















Using TeXMaker as the LaTeX editor I have been working with the MikTeX distribution for a number of years, successfully. Hearing it suggested that Tex Live may have a compilation speed advantage over MikTeX, I recently installed TexLive to see for myself, expecting that configuring TeXMaker to work with TeXLive in place of MiKTeX would be an easy thing. The Options menu offers Configure TeXMaker tab which provides fields LaTeX and PdfLaTeX presumably to be populated with the programs to be executed for LaTeX and PDFLaTeX compilations (function keys f2 and f6 respectively). Having found executables pdflatex.exe in C:/Users/Reinhard Neuwirth/AppData/Local/Programs/MikTeX 2.9/miktex/bin/X64 (my routinely used MikTeX distribution) as well as in C:/texlive/2018/bin/win32/ (the recently installed TeXLive distribution) I naively assumed that plugging either one or the other into the PDFLaTeX field would coerce TeXMaker to use the targeted distribution for compilation. Not so. The only entry in that field that seems to work is pdflatex -synctex=1 -interaction=nonstopmode %.tex, seemingly the default value - for the LaTeX field it is latex -interaction=nonstopmode %.tex.



The extensive discussion around the topic on the Stack Exchange, starting with Using MiKTeX and TeX Live on the same computer? asked Oct 11 '11 at 11:56 doncherry ... answered Oct 11 '11 at 12:21 Ulrike Fischer veers off into discussions of how to set PATHS in Windows etc., a place I don't want to go. Also, I am not at this stage interested in switching between MikTeX or TeXLive, just want to know how to configure TeXMaker to do one or the other through the Configure TeXMaker tab, if this can be done.



No MWE for this one.










share|improve this question


















  • 1





    Not tested, but maybe you could make use of Options --> configure TeXMaker --> Add to PATH.

    – leandriis
    yesterday











  • Looks like a possibility, but have not been able to make it perform as intended.

    – Reinhard Neuwirth
    yesterday
















2















Using TeXMaker as the LaTeX editor I have been working with the MikTeX distribution for a number of years, successfully. Hearing it suggested that Tex Live may have a compilation speed advantage over MikTeX, I recently installed TexLive to see for myself, expecting that configuring TeXMaker to work with TeXLive in place of MiKTeX would be an easy thing. The Options menu offers Configure TeXMaker tab which provides fields LaTeX and PdfLaTeX presumably to be populated with the programs to be executed for LaTeX and PDFLaTeX compilations (function keys f2 and f6 respectively). Having found executables pdflatex.exe in C:/Users/Reinhard Neuwirth/AppData/Local/Programs/MikTeX 2.9/miktex/bin/X64 (my routinely used MikTeX distribution) as well as in C:/texlive/2018/bin/win32/ (the recently installed TeXLive distribution) I naively assumed that plugging either one or the other into the PDFLaTeX field would coerce TeXMaker to use the targeted distribution for compilation. Not so. The only entry in that field that seems to work is pdflatex -synctex=1 -interaction=nonstopmode %.tex, seemingly the default value - for the LaTeX field it is latex -interaction=nonstopmode %.tex.



The extensive discussion around the topic on the Stack Exchange, starting with Using MiKTeX and TeX Live on the same computer? asked Oct 11 '11 at 11:56 doncherry ... answered Oct 11 '11 at 12:21 Ulrike Fischer veers off into discussions of how to set PATHS in Windows etc., a place I don't want to go. Also, I am not at this stage interested in switching between MikTeX or TeXLive, just want to know how to configure TeXMaker to do one or the other through the Configure TeXMaker tab, if this can be done.



No MWE for this one.










share|improve this question


















  • 1





    Not tested, but maybe you could make use of Options --> configure TeXMaker --> Add to PATH.

    – leandriis
    yesterday











  • Looks like a possibility, but have not been able to make it perform as intended.

    – Reinhard Neuwirth
    yesterday














2












2








2








Using TeXMaker as the LaTeX editor I have been working with the MikTeX distribution for a number of years, successfully. Hearing it suggested that Tex Live may have a compilation speed advantage over MikTeX, I recently installed TexLive to see for myself, expecting that configuring TeXMaker to work with TeXLive in place of MiKTeX would be an easy thing. The Options menu offers Configure TeXMaker tab which provides fields LaTeX and PdfLaTeX presumably to be populated with the programs to be executed for LaTeX and PDFLaTeX compilations (function keys f2 and f6 respectively). Having found executables pdflatex.exe in C:/Users/Reinhard Neuwirth/AppData/Local/Programs/MikTeX 2.9/miktex/bin/X64 (my routinely used MikTeX distribution) as well as in C:/texlive/2018/bin/win32/ (the recently installed TeXLive distribution) I naively assumed that plugging either one or the other into the PDFLaTeX field would coerce TeXMaker to use the targeted distribution for compilation. Not so. The only entry in that field that seems to work is pdflatex -synctex=1 -interaction=nonstopmode %.tex, seemingly the default value - for the LaTeX field it is latex -interaction=nonstopmode %.tex.



The extensive discussion around the topic on the Stack Exchange, starting with Using MiKTeX and TeX Live on the same computer? asked Oct 11 '11 at 11:56 doncherry ... answered Oct 11 '11 at 12:21 Ulrike Fischer veers off into discussions of how to set PATHS in Windows etc., a place I don't want to go. Also, I am not at this stage interested in switching between MikTeX or TeXLive, just want to know how to configure TeXMaker to do one or the other through the Configure TeXMaker tab, if this can be done.



No MWE for this one.










share|improve this question














Using TeXMaker as the LaTeX editor I have been working with the MikTeX distribution for a number of years, successfully. Hearing it suggested that Tex Live may have a compilation speed advantage over MikTeX, I recently installed TexLive to see for myself, expecting that configuring TeXMaker to work with TeXLive in place of MiKTeX would be an easy thing. The Options menu offers Configure TeXMaker tab which provides fields LaTeX and PdfLaTeX presumably to be populated with the programs to be executed for LaTeX and PDFLaTeX compilations (function keys f2 and f6 respectively). Having found executables pdflatex.exe in C:/Users/Reinhard Neuwirth/AppData/Local/Programs/MikTeX 2.9/miktex/bin/X64 (my routinely used MikTeX distribution) as well as in C:/texlive/2018/bin/win32/ (the recently installed TeXLive distribution) I naively assumed that plugging either one or the other into the PDFLaTeX field would coerce TeXMaker to use the targeted distribution for compilation. Not so. The only entry in that field that seems to work is pdflatex -synctex=1 -interaction=nonstopmode %.tex, seemingly the default value - for the LaTeX field it is latex -interaction=nonstopmode %.tex.



The extensive discussion around the topic on the Stack Exchange, starting with Using MiKTeX and TeX Live on the same computer? asked Oct 11 '11 at 11:56 doncherry ... answered Oct 11 '11 at 12:21 Ulrike Fischer veers off into discussions of how to set PATHS in Windows etc., a place I don't want to go. Also, I am not at this stage interested in switching between MikTeX or TeXLive, just want to know how to configure TeXMaker to do one or the other through the Configure TeXMaker tab, if this can be done.



No MWE for this one.







texmaker






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked yesterday









Reinhard NeuwirthReinhard Neuwirth

1,62111422




1,62111422








  • 1





    Not tested, but maybe you could make use of Options --> configure TeXMaker --> Add to PATH.

    – leandriis
    yesterday











  • Looks like a possibility, but have not been able to make it perform as intended.

    – Reinhard Neuwirth
    yesterday














  • 1





    Not tested, but maybe you could make use of Options --> configure TeXMaker --> Add to PATH.

    – leandriis
    yesterday











  • Looks like a possibility, but have not been able to make it perform as intended.

    – Reinhard Neuwirth
    yesterday








1




1





Not tested, but maybe you could make use of Options --> configure TeXMaker --> Add to PATH.

– leandriis
yesterday





Not tested, but maybe you could make use of Options --> configure TeXMaker --> Add to PATH.

– leandriis
yesterday













Looks like a possibility, but have not been able to make it perform as intended.

– Reinhard Neuwirth
yesterday





Looks like a possibility, but have not been able to make it perform as intended.

– Reinhard Neuwirth
yesterday










1 Answer
1






active

oldest

votes


















5














If you want to switch the texsystem you must change the path variable. The texsystems often call their tools themselves (e.g. to create a format or a tfm or search for files) and so must be able to find their own binaries. Simply trying to use C:texlive2018binwin32pdflatex.exe while everything else (including the kpathsea searches) points to miktex gives only chaos.



I don't know if texmaker has an option to change the path during a session -- with my editor winedt it is quite easy to do it on-the-fly by calling a macro.



But you can change the path to texlive between sessions rather easily:



Open a cmd window. Type



  set PATH=C:texlive2018binwin32;%PATH%


hit enter. Test if the correct pdflatex is found by typing



  where pdflatex


and then start texmaker from this cmd window by typing in the path to the texmaker exe.



If something doesn't work, simply close texmaker and the cmd window and the path will be back to normal.






share|improve this answer
























  • My current situation is that typing at the Command Prompt either set PATH=C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe;%PATH% or set PATH=C:texlive2018binwin32;%PATH% will result in C:UsersReinhard Neuwirth>where pdflatex C:texlive2018binwin32pdflatex.exe C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe. The response suggests that PATH is loaded with texlive and miktex. I am doing something wrong here.

    – Reinhard Neuwirth
    yesterday











  • … further, on the odd occasion where pdflatex produces the Windows operating system response 'where' is not recognized as an internal or external command, operable program or batch file.

    – Reinhard Neuwirth
    yesterday






  • 2





    if doesn't matter if both are in the path, the one found first is important.

    – Ulrike Fischer
    yesterday











  • All works as it should now!

    – Reinhard Neuwirth
    yesterday











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%2f479911%2fconfiguring-texmaker-to-work-with-the-texlive-distribution%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









5














If you want to switch the texsystem you must change the path variable. The texsystems often call their tools themselves (e.g. to create a format or a tfm or search for files) and so must be able to find their own binaries. Simply trying to use C:texlive2018binwin32pdflatex.exe while everything else (including the kpathsea searches) points to miktex gives only chaos.



I don't know if texmaker has an option to change the path during a session -- with my editor winedt it is quite easy to do it on-the-fly by calling a macro.



But you can change the path to texlive between sessions rather easily:



Open a cmd window. Type



  set PATH=C:texlive2018binwin32;%PATH%


hit enter. Test if the correct pdflatex is found by typing



  where pdflatex


and then start texmaker from this cmd window by typing in the path to the texmaker exe.



If something doesn't work, simply close texmaker and the cmd window and the path will be back to normal.






share|improve this answer
























  • My current situation is that typing at the Command Prompt either set PATH=C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe;%PATH% or set PATH=C:texlive2018binwin32;%PATH% will result in C:UsersReinhard Neuwirth>where pdflatex C:texlive2018binwin32pdflatex.exe C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe. The response suggests that PATH is loaded with texlive and miktex. I am doing something wrong here.

    – Reinhard Neuwirth
    yesterday











  • … further, on the odd occasion where pdflatex produces the Windows operating system response 'where' is not recognized as an internal or external command, operable program or batch file.

    – Reinhard Neuwirth
    yesterday






  • 2





    if doesn't matter if both are in the path, the one found first is important.

    – Ulrike Fischer
    yesterday











  • All works as it should now!

    – Reinhard Neuwirth
    yesterday
















5














If you want to switch the texsystem you must change the path variable. The texsystems often call their tools themselves (e.g. to create a format or a tfm or search for files) and so must be able to find their own binaries. Simply trying to use C:texlive2018binwin32pdflatex.exe while everything else (including the kpathsea searches) points to miktex gives only chaos.



I don't know if texmaker has an option to change the path during a session -- with my editor winedt it is quite easy to do it on-the-fly by calling a macro.



But you can change the path to texlive between sessions rather easily:



Open a cmd window. Type



  set PATH=C:texlive2018binwin32;%PATH%


hit enter. Test if the correct pdflatex is found by typing



  where pdflatex


and then start texmaker from this cmd window by typing in the path to the texmaker exe.



If something doesn't work, simply close texmaker and the cmd window and the path will be back to normal.






share|improve this answer
























  • My current situation is that typing at the Command Prompt either set PATH=C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe;%PATH% or set PATH=C:texlive2018binwin32;%PATH% will result in C:UsersReinhard Neuwirth>where pdflatex C:texlive2018binwin32pdflatex.exe C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe. The response suggests that PATH is loaded with texlive and miktex. I am doing something wrong here.

    – Reinhard Neuwirth
    yesterday











  • … further, on the odd occasion where pdflatex produces the Windows operating system response 'where' is not recognized as an internal or external command, operable program or batch file.

    – Reinhard Neuwirth
    yesterday






  • 2





    if doesn't matter if both are in the path, the one found first is important.

    – Ulrike Fischer
    yesterday











  • All works as it should now!

    – Reinhard Neuwirth
    yesterday














5












5








5







If you want to switch the texsystem you must change the path variable. The texsystems often call their tools themselves (e.g. to create a format or a tfm or search for files) and so must be able to find their own binaries. Simply trying to use C:texlive2018binwin32pdflatex.exe while everything else (including the kpathsea searches) points to miktex gives only chaos.



I don't know if texmaker has an option to change the path during a session -- with my editor winedt it is quite easy to do it on-the-fly by calling a macro.



But you can change the path to texlive between sessions rather easily:



Open a cmd window. Type



  set PATH=C:texlive2018binwin32;%PATH%


hit enter. Test if the correct pdflatex is found by typing



  where pdflatex


and then start texmaker from this cmd window by typing in the path to the texmaker exe.



If something doesn't work, simply close texmaker and the cmd window and the path will be back to normal.






share|improve this answer













If you want to switch the texsystem you must change the path variable. The texsystems often call their tools themselves (e.g. to create a format or a tfm or search for files) and so must be able to find their own binaries. Simply trying to use C:texlive2018binwin32pdflatex.exe while everything else (including the kpathsea searches) points to miktex gives only chaos.



I don't know if texmaker has an option to change the path during a session -- with my editor winedt it is quite easy to do it on-the-fly by calling a macro.



But you can change the path to texlive between sessions rather easily:



Open a cmd window. Type



  set PATH=C:texlive2018binwin32;%PATH%


hit enter. Test if the correct pdflatex is found by typing



  where pdflatex


and then start texmaker from this cmd window by typing in the path to the texmaker exe.



If something doesn't work, simply close texmaker and the cmd window and the path will be back to normal.







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









Ulrike FischerUlrike Fischer

196k8302689




196k8302689













  • My current situation is that typing at the Command Prompt either set PATH=C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe;%PATH% or set PATH=C:texlive2018binwin32;%PATH% will result in C:UsersReinhard Neuwirth>where pdflatex C:texlive2018binwin32pdflatex.exe C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe. The response suggests that PATH is loaded with texlive and miktex. I am doing something wrong here.

    – Reinhard Neuwirth
    yesterday











  • … further, on the odd occasion where pdflatex produces the Windows operating system response 'where' is not recognized as an internal or external command, operable program or batch file.

    – Reinhard Neuwirth
    yesterday






  • 2





    if doesn't matter if both are in the path, the one found first is important.

    – Ulrike Fischer
    yesterday











  • All works as it should now!

    – Reinhard Neuwirth
    yesterday



















  • My current situation is that typing at the Command Prompt either set PATH=C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe;%PATH% or set PATH=C:texlive2018binwin32;%PATH% will result in C:UsersReinhard Neuwirth>where pdflatex C:texlive2018binwin32pdflatex.exe C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe. The response suggests that PATH is loaded with texlive and miktex. I am doing something wrong here.

    – Reinhard Neuwirth
    yesterday











  • … further, on the odd occasion where pdflatex produces the Windows operating system response 'where' is not recognized as an internal or external command, operable program or batch file.

    – Reinhard Neuwirth
    yesterday






  • 2





    if doesn't matter if both are in the path, the one found first is important.

    – Ulrike Fischer
    yesterday











  • All works as it should now!

    – Reinhard Neuwirth
    yesterday

















My current situation is that typing at the Command Prompt either set PATH=C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe;%PATH% or set PATH=C:texlive2018binwin32;%PATH% will result in C:UsersReinhard Neuwirth>where pdflatex C:texlive2018binwin32pdflatex.exe C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe. The response suggests that PATH is loaded with texlive and miktex. I am doing something wrong here.

– Reinhard Neuwirth
yesterday





My current situation is that typing at the Command Prompt either set PATH=C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe;%PATH% or set PATH=C:texlive2018binwin32;%PATH% will result in C:UsersReinhard Neuwirth>where pdflatex C:texlive2018binwin32pdflatex.exe C:UsersReinhard NeuwirthAppDataLocalProgramsMiKTeX 2.9miktexbinx64pdflatex.exe. The response suggests that PATH is loaded with texlive and miktex. I am doing something wrong here.

– Reinhard Neuwirth
yesterday













… further, on the odd occasion where pdflatex produces the Windows operating system response 'where' is not recognized as an internal or external command, operable program or batch file.

– Reinhard Neuwirth
yesterday





… further, on the odd occasion where pdflatex produces the Windows operating system response 'where' is not recognized as an internal or external command, operable program or batch file.

– Reinhard Neuwirth
yesterday




2




2





if doesn't matter if both are in the path, the one found first is important.

– Ulrike Fischer
yesterday





if doesn't matter if both are in the path, the one found first is important.

– Ulrike Fischer
yesterday













All works as it should now!

– Reinhard Neuwirth
yesterday





All works as it should now!

– Reinhard Neuwirth
yesterday


















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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479911%2fconfiguring-texmaker-to-work-with-the-texlive-distribution%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

Plaza Victoria

Puebla de Zaragoza

Musa