Suppressing unwanted command line output when running pdflatexHebrew TeXLive on Ubuntu 12.04 missing...

How to show the equivalence between the regularized regression and their constraint formulas using KKT

I Accidentally Deleted a Stock Terminal Theme

What to put in ESTA if staying in US for a few days before going on to Canada

Neighboring nodes in the network

Assassin's bullet with mercury

Why can't we play rap on piano?

Fully-Firstable Anagram Sets

Emailing HOD to enhance faculty application

Facing a paradox: Earnshaw's theorem in one dimension

Famous Pre Reformation Christian Pastors (Non Catholic and Non Orthodox)

Alternative to sending password over mail?

Reserved de-dupe rules

How to draw the figure with four pentagons?

What does it mean to describe someone as a butt steak?

Combinations of multiple lists

Does casting Light, or a similar spell, have any effect when the caster is swallowed by a monster?

Is the Joker left-handed?

intersection of two sorted vectors in C++

What is the word for reserving something for yourself before others do?

How do conventional missiles fly?

Why is Collection not simply treated as Collection<?>

Will google still index a page if I use a $_SESSION variable?

Twin primes whose sum is a cube

Theorems that impeded progress



Suppressing unwanted command line output when running pdflatex


Hebrew TeXLive on Ubuntu 12.04 missing fontsStrange Error with Libertine and pdfpagesA package (installed according to TeX Live Utility) doesn't runCaption Error: “destination with the same identifier (name{figure.1}) has been already used”Auxhook warning cannot patch document using AtBeginDocument insteadPackage incompatibility issue?Error file.cls not found after updateError when using the amsthm packageTexlive 2017 texhash not workingbaposter.cls - problems with usetikzlibrary{snakes}













6















Using the batchmode command at the top of the file helps getting rid of some lines, but I'm still left with a few lines, for example:



(/usr/local/texlive/2011/texmf-dist/tex/latex/base/t1enc.def))
(/usr/local/texlive/2011/texmf-dist/tex/generic/babel/babel.sty
(/usr/local/texlive/2011/texmf-dist/tex/generic/babel/english.ldf



and so on.
I am unable to find a way to clear up my command line so that any warnings or lines that get printed to tell me something more useful don't just get lost in the sea of LaTeX output.



Any ideas?










share|improve this question





























    6















    Using the batchmode command at the top of the file helps getting rid of some lines, but I'm still left with a few lines, for example:



    (/usr/local/texlive/2011/texmf-dist/tex/latex/base/t1enc.def))
    (/usr/local/texlive/2011/texmf-dist/tex/generic/babel/babel.sty
    (/usr/local/texlive/2011/texmf-dist/tex/generic/babel/english.ldf



    and so on.
    I am unable to find a way to clear up my command line so that any warnings or lines that get printed to tell me something more useful don't just get lost in the sea of LaTeX output.



    Any ideas?










    share|improve this question



























      6












      6








      6








      Using the batchmode command at the top of the file helps getting rid of some lines, but I'm still left with a few lines, for example:



      (/usr/local/texlive/2011/texmf-dist/tex/latex/base/t1enc.def))
      (/usr/local/texlive/2011/texmf-dist/tex/generic/babel/babel.sty
      (/usr/local/texlive/2011/texmf-dist/tex/generic/babel/english.ldf



      and so on.
      I am unable to find a way to clear up my command line so that any warnings or lines that get printed to tell me something more useful don't just get lost in the sea of LaTeX output.



      Any ideas?










      share|improve this question
















      Using the batchmode command at the top of the file helps getting rid of some lines, but I'm still left with a few lines, for example:



      (/usr/local/texlive/2011/texmf-dist/tex/latex/base/t1enc.def))
      (/usr/local/texlive/2011/texmf-dist/tex/generic/babel/babel.sty
      (/usr/local/texlive/2011/texmf-dist/tex/generic/babel/english.ldf



      and so on.
      I am unable to find a way to clear up my command line so that any warnings or lines that get printed to tell me something more useful don't just get lost in the sea of LaTeX output.



      Any ideas?







      errors warnings






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 14 '13 at 12:43









      Joseph Wright

      205k23563891




      205k23563891










      asked Aug 14 '13 at 10:31









      user1488804user1488804

      18228




      18228






















          2 Answers
          2






          active

          oldest

          votes


















          9














          You can start batchmode earlier by specifying it on the commandline



          pdflatex -interaction=batchmode   myfile.tex


          Or if you don't even want



          This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
          restricted write18 enabled.
          entering extended mode


          You could use



          pdflatex  myfile > /dev/null


          or whatever null output stream is applicable to your operating system.






          share|improve this answer
























          • Unfortunately I don't think I'm able to use that command, since pdflatex is being called by another program. The line in the makefile that uses pdflatex does not allow these options to used.

            – user1488804
            Aug 14 '13 at 12:36











          • @user1488804 Well that's a Makefile problem, not a TeX one! Even so, I don't see that it makes sense either: you can happily redirect/add options in a Makefile.

            – Joseph Wright
            Aug 14 '13 at 12:40











          • I understand, but I do have freedom to add things to the latex preamble, so I was hoping the solution could be found there.

            – user1488804
            Aug 14 '13 at 13:01











          • And the line in the makefile isn't: pdflatex ... myfile.tex. Instead it's sphinx-build ... latex myfile.tex. Unfortunately, this program, sphinx, is a bit restrictive to what can be added here. Default pdflatex options don't work

            – user1488804
            Aug 14 '13 at 13:02













          • Ahah! the outputting stdout to /dev/null works in this case as it's not latex specific. Thanks!

            – user1488804
            Aug 15 '13 at 9:41



















          0














          When redirecting to /dev/null is a good solution for you, you might consider using grep to suppress "almost everything". I use this (with GNU grep 3.1) to find out whether another run of latex is needed (feel free to extend):



          egrep "Rerun to get cross-references right|
          There were undefined references|
          Citation .* on page .* undefined on input"


          I know this type of matching is dangerous (future versions, localization, etc.), but it works ;-)






          share|improve this answer
























            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%2f128176%2fsuppressing-unwanted-command-line-output-when-running-pdflatex%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            9














            You can start batchmode earlier by specifying it on the commandline



            pdflatex -interaction=batchmode   myfile.tex


            Or if you don't even want



            This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
            restricted write18 enabled.
            entering extended mode


            You could use



            pdflatex  myfile > /dev/null


            or whatever null output stream is applicable to your operating system.






            share|improve this answer
























            • Unfortunately I don't think I'm able to use that command, since pdflatex is being called by another program. The line in the makefile that uses pdflatex does not allow these options to used.

              – user1488804
              Aug 14 '13 at 12:36











            • @user1488804 Well that's a Makefile problem, not a TeX one! Even so, I don't see that it makes sense either: you can happily redirect/add options in a Makefile.

              – Joseph Wright
              Aug 14 '13 at 12:40











            • I understand, but I do have freedom to add things to the latex preamble, so I was hoping the solution could be found there.

              – user1488804
              Aug 14 '13 at 13:01











            • And the line in the makefile isn't: pdflatex ... myfile.tex. Instead it's sphinx-build ... latex myfile.tex. Unfortunately, this program, sphinx, is a bit restrictive to what can be added here. Default pdflatex options don't work

              – user1488804
              Aug 14 '13 at 13:02













            • Ahah! the outputting stdout to /dev/null works in this case as it's not latex specific. Thanks!

              – user1488804
              Aug 15 '13 at 9:41
















            9














            You can start batchmode earlier by specifying it on the commandline



            pdflatex -interaction=batchmode   myfile.tex


            Or if you don't even want



            This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
            restricted write18 enabled.
            entering extended mode


            You could use



            pdflatex  myfile > /dev/null


            or whatever null output stream is applicable to your operating system.






            share|improve this answer
























            • Unfortunately I don't think I'm able to use that command, since pdflatex is being called by another program. The line in the makefile that uses pdflatex does not allow these options to used.

              – user1488804
              Aug 14 '13 at 12:36











            • @user1488804 Well that's a Makefile problem, not a TeX one! Even so, I don't see that it makes sense either: you can happily redirect/add options in a Makefile.

              – Joseph Wright
              Aug 14 '13 at 12:40











            • I understand, but I do have freedom to add things to the latex preamble, so I was hoping the solution could be found there.

              – user1488804
              Aug 14 '13 at 13:01











            • And the line in the makefile isn't: pdflatex ... myfile.tex. Instead it's sphinx-build ... latex myfile.tex. Unfortunately, this program, sphinx, is a bit restrictive to what can be added here. Default pdflatex options don't work

              – user1488804
              Aug 14 '13 at 13:02













            • Ahah! the outputting stdout to /dev/null works in this case as it's not latex specific. Thanks!

              – user1488804
              Aug 15 '13 at 9:41














            9












            9








            9







            You can start batchmode earlier by specifying it on the commandline



            pdflatex -interaction=batchmode   myfile.tex


            Or if you don't even want



            This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
            restricted write18 enabled.
            entering extended mode


            You could use



            pdflatex  myfile > /dev/null


            or whatever null output stream is applicable to your operating system.






            share|improve this answer













            You can start batchmode earlier by specifying it on the commandline



            pdflatex -interaction=batchmode   myfile.tex


            Or if you don't even want



            This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
            restricted write18 enabled.
            entering extended mode


            You could use



            pdflatex  myfile > /dev/null


            or whatever null output stream is applicable to your operating system.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Aug 14 '13 at 12:18









            David CarlisleDavid Carlisle

            497k4111441891




            497k4111441891













            • Unfortunately I don't think I'm able to use that command, since pdflatex is being called by another program. The line in the makefile that uses pdflatex does not allow these options to used.

              – user1488804
              Aug 14 '13 at 12:36











            • @user1488804 Well that's a Makefile problem, not a TeX one! Even so, I don't see that it makes sense either: you can happily redirect/add options in a Makefile.

              – Joseph Wright
              Aug 14 '13 at 12:40











            • I understand, but I do have freedom to add things to the latex preamble, so I was hoping the solution could be found there.

              – user1488804
              Aug 14 '13 at 13:01











            • And the line in the makefile isn't: pdflatex ... myfile.tex. Instead it's sphinx-build ... latex myfile.tex. Unfortunately, this program, sphinx, is a bit restrictive to what can be added here. Default pdflatex options don't work

              – user1488804
              Aug 14 '13 at 13:02













            • Ahah! the outputting stdout to /dev/null works in this case as it's not latex specific. Thanks!

              – user1488804
              Aug 15 '13 at 9:41



















            • Unfortunately I don't think I'm able to use that command, since pdflatex is being called by another program. The line in the makefile that uses pdflatex does not allow these options to used.

              – user1488804
              Aug 14 '13 at 12:36











            • @user1488804 Well that's a Makefile problem, not a TeX one! Even so, I don't see that it makes sense either: you can happily redirect/add options in a Makefile.

              – Joseph Wright
              Aug 14 '13 at 12:40











            • I understand, but I do have freedom to add things to the latex preamble, so I was hoping the solution could be found there.

              – user1488804
              Aug 14 '13 at 13:01











            • And the line in the makefile isn't: pdflatex ... myfile.tex. Instead it's sphinx-build ... latex myfile.tex. Unfortunately, this program, sphinx, is a bit restrictive to what can be added here. Default pdflatex options don't work

              – user1488804
              Aug 14 '13 at 13:02













            • Ahah! the outputting stdout to /dev/null works in this case as it's not latex specific. Thanks!

              – user1488804
              Aug 15 '13 at 9:41

















            Unfortunately I don't think I'm able to use that command, since pdflatex is being called by another program. The line in the makefile that uses pdflatex does not allow these options to used.

            – user1488804
            Aug 14 '13 at 12:36





            Unfortunately I don't think I'm able to use that command, since pdflatex is being called by another program. The line in the makefile that uses pdflatex does not allow these options to used.

            – user1488804
            Aug 14 '13 at 12:36













            @user1488804 Well that's a Makefile problem, not a TeX one! Even so, I don't see that it makes sense either: you can happily redirect/add options in a Makefile.

            – Joseph Wright
            Aug 14 '13 at 12:40





            @user1488804 Well that's a Makefile problem, not a TeX one! Even so, I don't see that it makes sense either: you can happily redirect/add options in a Makefile.

            – Joseph Wright
            Aug 14 '13 at 12:40













            I understand, but I do have freedom to add things to the latex preamble, so I was hoping the solution could be found there.

            – user1488804
            Aug 14 '13 at 13:01





            I understand, but I do have freedom to add things to the latex preamble, so I was hoping the solution could be found there.

            – user1488804
            Aug 14 '13 at 13:01













            And the line in the makefile isn't: pdflatex ... myfile.tex. Instead it's sphinx-build ... latex myfile.tex. Unfortunately, this program, sphinx, is a bit restrictive to what can be added here. Default pdflatex options don't work

            – user1488804
            Aug 14 '13 at 13:02







            And the line in the makefile isn't: pdflatex ... myfile.tex. Instead it's sphinx-build ... latex myfile.tex. Unfortunately, this program, sphinx, is a bit restrictive to what can be added here. Default pdflatex options don't work

            – user1488804
            Aug 14 '13 at 13:02















            Ahah! the outputting stdout to /dev/null works in this case as it's not latex specific. Thanks!

            – user1488804
            Aug 15 '13 at 9:41





            Ahah! the outputting stdout to /dev/null works in this case as it's not latex specific. Thanks!

            – user1488804
            Aug 15 '13 at 9:41











            0














            When redirecting to /dev/null is a good solution for you, you might consider using grep to suppress "almost everything". I use this (with GNU grep 3.1) to find out whether another run of latex is needed (feel free to extend):



            egrep "Rerun to get cross-references right|
            There were undefined references|
            Citation .* on page .* undefined on input"


            I know this type of matching is dangerous (future versions, localization, etc.), but it works ;-)






            share|improve this answer




























              0














              When redirecting to /dev/null is a good solution for you, you might consider using grep to suppress "almost everything". I use this (with GNU grep 3.1) to find out whether another run of latex is needed (feel free to extend):



              egrep "Rerun to get cross-references right|
              There were undefined references|
              Citation .* on page .* undefined on input"


              I know this type of matching is dangerous (future versions, localization, etc.), but it works ;-)






              share|improve this answer


























                0












                0








                0







                When redirecting to /dev/null is a good solution for you, you might consider using grep to suppress "almost everything". I use this (with GNU grep 3.1) to find out whether another run of latex is needed (feel free to extend):



                egrep "Rerun to get cross-references right|
                There were undefined references|
                Citation .* on page .* undefined on input"


                I know this type of matching is dangerous (future versions, localization, etc.), but it works ;-)






                share|improve this answer













                When redirecting to /dev/null is a good solution for you, you might consider using grep to suppress "almost everything". I use this (with GNU grep 3.1) to find out whether another run of latex is needed (feel free to extend):



                egrep "Rerun to get cross-references right|
                There were undefined references|
                Citation .* on page .* undefined on input"


                I know this type of matching is dangerous (future versions, localization, etc.), but it works ;-)







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 4 hours ago









                U. WindlU. Windl

                1477




                1477






























                    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%2f128176%2fsuppressing-unwanted-command-line-output-when-running-pdflatex%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

                    Installing LyX: “No textclass is found.”LyX installation error- text class not found- 'Reconfigure' or...

                    (1602) Indiana Índice Designación y nombre Características orbitales Véase...

                    Universidad Autónoma de Occidente Índice Historia Campus Facultades Programas Académicos Medios de...