pdflatex commandline hide compilation output











up vote
10
down vote

favorite
1












My program produces multiple outputs: I have a .tex file compiled, and some of them are produced in the command-line. The compilation info of pdf-latex is useless to me and I would like to hide it to make my command-line output readable.



I have seen this site mention some box-thicking should do it, but I haven't found a command-line equivalent.










share|improve this question















migrated from stackoverflow.com Mar 20 '14 at 12:48


This question came from our site for professional and enthusiast programmers.



















    up vote
    10
    down vote

    favorite
    1












    My program produces multiple outputs: I have a .tex file compiled, and some of them are produced in the command-line. The compilation info of pdf-latex is useless to me and I would like to hide it to make my command-line output readable.



    I have seen this site mention some box-thicking should do it, but I haven't found a command-line equivalent.










    share|improve this question















    migrated from stackoverflow.com Mar 20 '14 at 12:48


    This question came from our site for professional and enthusiast programmers.

















      up vote
      10
      down vote

      favorite
      1









      up vote
      10
      down vote

      favorite
      1






      1





      My program produces multiple outputs: I have a .tex file compiled, and some of them are produced in the command-line. The compilation info of pdf-latex is useless to me and I would like to hide it to make my command-line output readable.



      I have seen this site mention some box-thicking should do it, but I haven't found a command-line equivalent.










      share|improve this question















      My program produces multiple outputs: I have a .tex file compiled, and some of them are produced in the command-line. The compilation info of pdf-latex is useless to me and I would like to hide it to make my command-line output readable.



      I have seen this site mention some box-thicking should do it, but I haven't found a command-line equivalent.







      terminal-output






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 11 '15 at 0:08









      Paul Gessler

      22.7k474171




      22.7k474171










      asked Mar 19 '14 at 8:08







      Haxelaar











      migrated from stackoverflow.com Mar 20 '14 at 12:48


      This question came from our site for professional and enthusiast programmers.






      migrated from stackoverflow.com Mar 20 '14 at 12:48


      This question came from our site for professional and enthusiast programmers.
























          3 Answers
          3






          active

          oldest

          votes

















          up vote
          11
          down vote



          accepted










          You can either redirect all of the pdflatex output:




          • for sh: pdflatex ... > /dev/null 2>&1

          • for cmd: pdflatex ... > NUL 2>&1


          Or you can use the -quiet option:



          pdflatex -quiet ...





          share|improve this answer

















          • 1




            the quiet-option would be perfect, but "pdflatex: unrecognized option '-quiet'"
            – Haxelaar
            Mar 19 '14 at 8:19






          • 2




            @Haxelaar Hmm, it seems to be present for the MiKTeX 2.9 pdflatex version, but the Arch Linux TeXLive version does not have it indeed. Then redirecting output is your only option. You can leave out the 2>&1 bit if you still want to show errors (and maybe warnings, depending on how pdflatex outputs them).
            – rubenvb
            Mar 19 '14 at 8:36






          • 6




            Using pdflatex --interaction=batchmode ... hides almost all of the output
            – Andrew
            Mar 2 '17 at 1:51


















          up vote
          4
          down vote















          In my case, there is no -quiet mode. So I had to use -interaction=batchmode argument as suggeseted by Andrew's comment.



          But then another problem arised - you will not see what went wrong and why, because errors are also suppressed with batchmode.



          The result I end up using is to suppress all pdflatex's output by using grep to output only errors:



          : | pdflatex -halt-on-error src.tex | grep '^!.*' -A200 --color=always 


          I use -halt-on-error because you basically can't use interactive mode in case of error (grep disables dialog between program and user). Also, to make sure that pdflatex does never prompt for the input, let's pipe in command with no output (: command).



          Let me also explain the grep arguments:





          • ^!.*


            • string to search for in the output from pdflatex

            • it matches all lines that start with !, which are considered error lines




          • -A200


            • output 200 lines after every match

            • this way I make sure to print also the relevant information followed after the matched error lines




          • --color=always


            • this provides us colored output so that we can clearly see what went wrong and why - the problem is bold red






          Wrapper script



          I've created a wrapper script to provide more convenient solution exactly for this purpose. It's usage is almost the same as pdflatex / pdftex itself. You can check it out as a CTAN package or as a GitLab repository.



          Quickinstall



          And here is how to install the latest version using this oneliner:



          curl -s https://gitlab.com/jirislav/pdftex-quiet/raw/latest/pdftex-quiet | 
          sudo tee /usr/local/bin/pdftex-quiet >/dev/null
          && sudo chmod +x /usr/local/bin/pdftex-quiet
          && sudo ln -sf /usr/local/bin/pdftex-quiet /usr/local/bin/pdflatex-quiet


          Here is an example of how you run the wrapper script:



          pdftex-quiet compile-me.tex
          # You may also provide additional attributes to `pdflatex`
          pdflatex-quiet -output-format=dvi -output-directory=/tmp compile-me.tex


          You can also show version or help of the pdflatex-quiet / pdftex-quiet script:



          pdflatex-quiet -v  # or --version
          pdflatex-quiet -h # or --help


          Also the difference between pdflatex-quiet and pdftex-quiet, as explained here is respected - thanks to Denis Bitouzé's comment.






          share|improve this answer










          New contributor




          jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















          • Welcome to TeX.SX! Very nice contribution!
            – egreg
            Nov 11 at 15:09










          • Thank you :) I've further improved the proposed answer so that it has disabled stdin when running pdflatex with : command, because it would seem to hang up when it prompts for input (grep doesn't print characters until newline is printed, so you can't possibly know what it's waiting for). Oh and I've found out that pdflatex always prints ! at the start of the line describing problem, so I've also updated the grep expression and added colored output so that you see exactly what have failed. And finally, I've added final pdf/div filename to be printed in the bash script on success.
            – jirislav
            Nov 11 at 16:34












          • Would you like to submit it to CTAN?
            – egreg
            Nov 11 at 16:46










          • I've never submitted anything there until now :) .. I've called it pdfla­tex-quiet
            – jirislav
            Nov 11 at 17:30










          • perhaps you could get in touch with Latexmk maintainer and suggest incorporation into it
            – jfbu
            Nov 12 at 22:31


















          up vote
          3
          down vote













          FWIW, https://ctan.org/pkg/texfot was my attempt at solving this problem -- eliminating the verbose output from tex engines while still showing the interesting messages (the ones I actually want to do something about). --karl






          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',
            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%2f166658%2fpdflatex-commandline-hide-compilation-output%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown
























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            11
            down vote



            accepted










            You can either redirect all of the pdflatex output:




            • for sh: pdflatex ... > /dev/null 2>&1

            • for cmd: pdflatex ... > NUL 2>&1


            Or you can use the -quiet option:



            pdflatex -quiet ...





            share|improve this answer

















            • 1




              the quiet-option would be perfect, but "pdflatex: unrecognized option '-quiet'"
              – Haxelaar
              Mar 19 '14 at 8:19






            • 2




              @Haxelaar Hmm, it seems to be present for the MiKTeX 2.9 pdflatex version, but the Arch Linux TeXLive version does not have it indeed. Then redirecting output is your only option. You can leave out the 2>&1 bit if you still want to show errors (and maybe warnings, depending on how pdflatex outputs them).
              – rubenvb
              Mar 19 '14 at 8:36






            • 6




              Using pdflatex --interaction=batchmode ... hides almost all of the output
              – Andrew
              Mar 2 '17 at 1:51















            up vote
            11
            down vote



            accepted










            You can either redirect all of the pdflatex output:




            • for sh: pdflatex ... > /dev/null 2>&1

            • for cmd: pdflatex ... > NUL 2>&1


            Or you can use the -quiet option:



            pdflatex -quiet ...





            share|improve this answer

















            • 1




              the quiet-option would be perfect, but "pdflatex: unrecognized option '-quiet'"
              – Haxelaar
              Mar 19 '14 at 8:19






            • 2




              @Haxelaar Hmm, it seems to be present for the MiKTeX 2.9 pdflatex version, but the Arch Linux TeXLive version does not have it indeed. Then redirecting output is your only option. You can leave out the 2>&1 bit if you still want to show errors (and maybe warnings, depending on how pdflatex outputs them).
              – rubenvb
              Mar 19 '14 at 8:36






            • 6




              Using pdflatex --interaction=batchmode ... hides almost all of the output
              – Andrew
              Mar 2 '17 at 1:51













            up vote
            11
            down vote



            accepted







            up vote
            11
            down vote



            accepted






            You can either redirect all of the pdflatex output:




            • for sh: pdflatex ... > /dev/null 2>&1

            • for cmd: pdflatex ... > NUL 2>&1


            Or you can use the -quiet option:



            pdflatex -quiet ...





            share|improve this answer












            You can either redirect all of the pdflatex output:




            • for sh: pdflatex ... > /dev/null 2>&1

            • for cmd: pdflatex ... > NUL 2>&1


            Or you can use the -quiet option:



            pdflatex -quiet ...






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 19 '14 at 8:14









            rubenvb

            1,83321626




            1,83321626








            • 1




              the quiet-option would be perfect, but "pdflatex: unrecognized option '-quiet'"
              – Haxelaar
              Mar 19 '14 at 8:19






            • 2




              @Haxelaar Hmm, it seems to be present for the MiKTeX 2.9 pdflatex version, but the Arch Linux TeXLive version does not have it indeed. Then redirecting output is your only option. You can leave out the 2>&1 bit if you still want to show errors (and maybe warnings, depending on how pdflatex outputs them).
              – rubenvb
              Mar 19 '14 at 8:36






            • 6




              Using pdflatex --interaction=batchmode ... hides almost all of the output
              – Andrew
              Mar 2 '17 at 1:51














            • 1




              the quiet-option would be perfect, but "pdflatex: unrecognized option '-quiet'"
              – Haxelaar
              Mar 19 '14 at 8:19






            • 2




              @Haxelaar Hmm, it seems to be present for the MiKTeX 2.9 pdflatex version, but the Arch Linux TeXLive version does not have it indeed. Then redirecting output is your only option. You can leave out the 2>&1 bit if you still want to show errors (and maybe warnings, depending on how pdflatex outputs them).
              – rubenvb
              Mar 19 '14 at 8:36






            • 6




              Using pdflatex --interaction=batchmode ... hides almost all of the output
              – Andrew
              Mar 2 '17 at 1:51








            1




            1




            the quiet-option would be perfect, but "pdflatex: unrecognized option '-quiet'"
            – Haxelaar
            Mar 19 '14 at 8:19




            the quiet-option would be perfect, but "pdflatex: unrecognized option '-quiet'"
            – Haxelaar
            Mar 19 '14 at 8:19




            2




            2




            @Haxelaar Hmm, it seems to be present for the MiKTeX 2.9 pdflatex version, but the Arch Linux TeXLive version does not have it indeed. Then redirecting output is your only option. You can leave out the 2>&1 bit if you still want to show errors (and maybe warnings, depending on how pdflatex outputs them).
            – rubenvb
            Mar 19 '14 at 8:36




            @Haxelaar Hmm, it seems to be present for the MiKTeX 2.9 pdflatex version, but the Arch Linux TeXLive version does not have it indeed. Then redirecting output is your only option. You can leave out the 2>&1 bit if you still want to show errors (and maybe warnings, depending on how pdflatex outputs them).
            – rubenvb
            Mar 19 '14 at 8:36




            6




            6




            Using pdflatex --interaction=batchmode ... hides almost all of the output
            – Andrew
            Mar 2 '17 at 1:51




            Using pdflatex --interaction=batchmode ... hides almost all of the output
            – Andrew
            Mar 2 '17 at 1:51










            up vote
            4
            down vote















            In my case, there is no -quiet mode. So I had to use -interaction=batchmode argument as suggeseted by Andrew's comment.



            But then another problem arised - you will not see what went wrong and why, because errors are also suppressed with batchmode.



            The result I end up using is to suppress all pdflatex's output by using grep to output only errors:



            : | pdflatex -halt-on-error src.tex | grep '^!.*' -A200 --color=always 


            I use -halt-on-error because you basically can't use interactive mode in case of error (grep disables dialog between program and user). Also, to make sure that pdflatex does never prompt for the input, let's pipe in command with no output (: command).



            Let me also explain the grep arguments:





            • ^!.*


              • string to search for in the output from pdflatex

              • it matches all lines that start with !, which are considered error lines




            • -A200


              • output 200 lines after every match

              • this way I make sure to print also the relevant information followed after the matched error lines




            • --color=always


              • this provides us colored output so that we can clearly see what went wrong and why - the problem is bold red






            Wrapper script



            I've created a wrapper script to provide more convenient solution exactly for this purpose. It's usage is almost the same as pdflatex / pdftex itself. You can check it out as a CTAN package or as a GitLab repository.



            Quickinstall



            And here is how to install the latest version using this oneliner:



            curl -s https://gitlab.com/jirislav/pdftex-quiet/raw/latest/pdftex-quiet | 
            sudo tee /usr/local/bin/pdftex-quiet >/dev/null
            && sudo chmod +x /usr/local/bin/pdftex-quiet
            && sudo ln -sf /usr/local/bin/pdftex-quiet /usr/local/bin/pdflatex-quiet


            Here is an example of how you run the wrapper script:



            pdftex-quiet compile-me.tex
            # You may also provide additional attributes to `pdflatex`
            pdflatex-quiet -output-format=dvi -output-directory=/tmp compile-me.tex


            You can also show version or help of the pdflatex-quiet / pdftex-quiet script:



            pdflatex-quiet -v  # or --version
            pdflatex-quiet -h # or --help


            Also the difference between pdflatex-quiet and pdftex-quiet, as explained here is respected - thanks to Denis Bitouzé's comment.






            share|improve this answer










            New contributor




            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.


















            • Welcome to TeX.SX! Very nice contribution!
              – egreg
              Nov 11 at 15:09










            • Thank you :) I've further improved the proposed answer so that it has disabled stdin when running pdflatex with : command, because it would seem to hang up when it prompts for input (grep doesn't print characters until newline is printed, so you can't possibly know what it's waiting for). Oh and I've found out that pdflatex always prints ! at the start of the line describing problem, so I've also updated the grep expression and added colored output so that you see exactly what have failed. And finally, I've added final pdf/div filename to be printed in the bash script on success.
              – jirislav
              Nov 11 at 16:34












            • Would you like to submit it to CTAN?
              – egreg
              Nov 11 at 16:46










            • I've never submitted anything there until now :) .. I've called it pdfla­tex-quiet
              – jirislav
              Nov 11 at 17:30










            • perhaps you could get in touch with Latexmk maintainer and suggest incorporation into it
              – jfbu
              Nov 12 at 22:31















            up vote
            4
            down vote















            In my case, there is no -quiet mode. So I had to use -interaction=batchmode argument as suggeseted by Andrew's comment.



            But then another problem arised - you will not see what went wrong and why, because errors are also suppressed with batchmode.



            The result I end up using is to suppress all pdflatex's output by using grep to output only errors:



            : | pdflatex -halt-on-error src.tex | grep '^!.*' -A200 --color=always 


            I use -halt-on-error because you basically can't use interactive mode in case of error (grep disables dialog between program and user). Also, to make sure that pdflatex does never prompt for the input, let's pipe in command with no output (: command).



            Let me also explain the grep arguments:





            • ^!.*


              • string to search for in the output from pdflatex

              • it matches all lines that start with !, which are considered error lines




            • -A200


              • output 200 lines after every match

              • this way I make sure to print also the relevant information followed after the matched error lines




            • --color=always


              • this provides us colored output so that we can clearly see what went wrong and why - the problem is bold red






            Wrapper script



            I've created a wrapper script to provide more convenient solution exactly for this purpose. It's usage is almost the same as pdflatex / pdftex itself. You can check it out as a CTAN package or as a GitLab repository.



            Quickinstall



            And here is how to install the latest version using this oneliner:



            curl -s https://gitlab.com/jirislav/pdftex-quiet/raw/latest/pdftex-quiet | 
            sudo tee /usr/local/bin/pdftex-quiet >/dev/null
            && sudo chmod +x /usr/local/bin/pdftex-quiet
            && sudo ln -sf /usr/local/bin/pdftex-quiet /usr/local/bin/pdflatex-quiet


            Here is an example of how you run the wrapper script:



            pdftex-quiet compile-me.tex
            # You may also provide additional attributes to `pdflatex`
            pdflatex-quiet -output-format=dvi -output-directory=/tmp compile-me.tex


            You can also show version or help of the pdflatex-quiet / pdftex-quiet script:



            pdflatex-quiet -v  # or --version
            pdflatex-quiet -h # or --help


            Also the difference between pdflatex-quiet and pdftex-quiet, as explained here is respected - thanks to Denis Bitouzé's comment.






            share|improve this answer










            New contributor




            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.


















            • Welcome to TeX.SX! Very nice contribution!
              – egreg
              Nov 11 at 15:09










            • Thank you :) I've further improved the proposed answer so that it has disabled stdin when running pdflatex with : command, because it would seem to hang up when it prompts for input (grep doesn't print characters until newline is printed, so you can't possibly know what it's waiting for). Oh and I've found out that pdflatex always prints ! at the start of the line describing problem, so I've also updated the grep expression and added colored output so that you see exactly what have failed. And finally, I've added final pdf/div filename to be printed in the bash script on success.
              – jirislav
              Nov 11 at 16:34












            • Would you like to submit it to CTAN?
              – egreg
              Nov 11 at 16:46










            • I've never submitted anything there until now :) .. I've called it pdfla­tex-quiet
              – jirislav
              Nov 11 at 17:30










            • perhaps you could get in touch with Latexmk maintainer and suggest incorporation into it
              – jfbu
              Nov 12 at 22:31













            up vote
            4
            down vote










            up vote
            4
            down vote











            In my case, there is no -quiet mode. So I had to use -interaction=batchmode argument as suggeseted by Andrew's comment.



            But then another problem arised - you will not see what went wrong and why, because errors are also suppressed with batchmode.



            The result I end up using is to suppress all pdflatex's output by using grep to output only errors:



            : | pdflatex -halt-on-error src.tex | grep '^!.*' -A200 --color=always 


            I use -halt-on-error because you basically can't use interactive mode in case of error (grep disables dialog between program and user). Also, to make sure that pdflatex does never prompt for the input, let's pipe in command with no output (: command).



            Let me also explain the grep arguments:





            • ^!.*


              • string to search for in the output from pdflatex

              • it matches all lines that start with !, which are considered error lines




            • -A200


              • output 200 lines after every match

              • this way I make sure to print also the relevant information followed after the matched error lines




            • --color=always


              • this provides us colored output so that we can clearly see what went wrong and why - the problem is bold red






            Wrapper script



            I've created a wrapper script to provide more convenient solution exactly for this purpose. It's usage is almost the same as pdflatex / pdftex itself. You can check it out as a CTAN package or as a GitLab repository.



            Quickinstall



            And here is how to install the latest version using this oneliner:



            curl -s https://gitlab.com/jirislav/pdftex-quiet/raw/latest/pdftex-quiet | 
            sudo tee /usr/local/bin/pdftex-quiet >/dev/null
            && sudo chmod +x /usr/local/bin/pdftex-quiet
            && sudo ln -sf /usr/local/bin/pdftex-quiet /usr/local/bin/pdflatex-quiet


            Here is an example of how you run the wrapper script:



            pdftex-quiet compile-me.tex
            # You may also provide additional attributes to `pdflatex`
            pdflatex-quiet -output-format=dvi -output-directory=/tmp compile-me.tex


            You can also show version or help of the pdflatex-quiet / pdftex-quiet script:



            pdflatex-quiet -v  # or --version
            pdflatex-quiet -h # or --help


            Also the difference between pdflatex-quiet and pdftex-quiet, as explained here is respected - thanks to Denis Bitouzé's comment.






            share|improve this answer










            New contributor




            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.











            In my case, there is no -quiet mode. So I had to use -interaction=batchmode argument as suggeseted by Andrew's comment.



            But then another problem arised - you will not see what went wrong and why, because errors are also suppressed with batchmode.



            The result I end up using is to suppress all pdflatex's output by using grep to output only errors:



            : | pdflatex -halt-on-error src.tex | grep '^!.*' -A200 --color=always 


            I use -halt-on-error because you basically can't use interactive mode in case of error (grep disables dialog between program and user). Also, to make sure that pdflatex does never prompt for the input, let's pipe in command with no output (: command).



            Let me also explain the grep arguments:





            • ^!.*


              • string to search for in the output from pdflatex

              • it matches all lines that start with !, which are considered error lines




            • -A200


              • output 200 lines after every match

              • this way I make sure to print also the relevant information followed after the matched error lines




            • --color=always


              • this provides us colored output so that we can clearly see what went wrong and why - the problem is bold red






            Wrapper script



            I've created a wrapper script to provide more convenient solution exactly for this purpose. It's usage is almost the same as pdflatex / pdftex itself. You can check it out as a CTAN package or as a GitLab repository.



            Quickinstall



            And here is how to install the latest version using this oneliner:



            curl -s https://gitlab.com/jirislav/pdftex-quiet/raw/latest/pdftex-quiet | 
            sudo tee /usr/local/bin/pdftex-quiet >/dev/null
            && sudo chmod +x /usr/local/bin/pdftex-quiet
            && sudo ln -sf /usr/local/bin/pdftex-quiet /usr/local/bin/pdflatex-quiet


            Here is an example of how you run the wrapper script:



            pdftex-quiet compile-me.tex
            # You may also provide additional attributes to `pdflatex`
            pdflatex-quiet -output-format=dvi -output-directory=/tmp compile-me.tex


            You can also show version or help of the pdflatex-quiet / pdftex-quiet script:



            pdflatex-quiet -v  # or --version
            pdflatex-quiet -h # or --help


            Also the difference between pdflatex-quiet and pdftex-quiet, as explained here is respected - thanks to Denis Bitouzé's comment.







            share|improve this answer










            New contributor




            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            share|improve this answer



            share|improve this answer








            edited Nov 14 at 23:17





















            New contributor




            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            answered Nov 11 at 14:43









            jirislav

            413




            413




            New contributor




            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





            New contributor





            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.






            jirislav is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.












            • Welcome to TeX.SX! Very nice contribution!
              – egreg
              Nov 11 at 15:09










            • Thank you :) I've further improved the proposed answer so that it has disabled stdin when running pdflatex with : command, because it would seem to hang up when it prompts for input (grep doesn't print characters until newline is printed, so you can't possibly know what it's waiting for). Oh and I've found out that pdflatex always prints ! at the start of the line describing problem, so I've also updated the grep expression and added colored output so that you see exactly what have failed. And finally, I've added final pdf/div filename to be printed in the bash script on success.
              – jirislav
              Nov 11 at 16:34












            • Would you like to submit it to CTAN?
              – egreg
              Nov 11 at 16:46










            • I've never submitted anything there until now :) .. I've called it pdfla­tex-quiet
              – jirislav
              Nov 11 at 17:30










            • perhaps you could get in touch with Latexmk maintainer and suggest incorporation into it
              – jfbu
              Nov 12 at 22:31


















            • Welcome to TeX.SX! Very nice contribution!
              – egreg
              Nov 11 at 15:09










            • Thank you :) I've further improved the proposed answer so that it has disabled stdin when running pdflatex with : command, because it would seem to hang up when it prompts for input (grep doesn't print characters until newline is printed, so you can't possibly know what it's waiting for). Oh and I've found out that pdflatex always prints ! at the start of the line describing problem, so I've also updated the grep expression and added colored output so that you see exactly what have failed. And finally, I've added final pdf/div filename to be printed in the bash script on success.
              – jirislav
              Nov 11 at 16:34












            • Would you like to submit it to CTAN?
              – egreg
              Nov 11 at 16:46










            • I've never submitted anything there until now :) .. I've called it pdfla­tex-quiet
              – jirislav
              Nov 11 at 17:30










            • perhaps you could get in touch with Latexmk maintainer and suggest incorporation into it
              – jfbu
              Nov 12 at 22:31
















            Welcome to TeX.SX! Very nice contribution!
            – egreg
            Nov 11 at 15:09




            Welcome to TeX.SX! Very nice contribution!
            – egreg
            Nov 11 at 15:09












            Thank you :) I've further improved the proposed answer so that it has disabled stdin when running pdflatex with : command, because it would seem to hang up when it prompts for input (grep doesn't print characters until newline is printed, so you can't possibly know what it's waiting for). Oh and I've found out that pdflatex always prints ! at the start of the line describing problem, so I've also updated the grep expression and added colored output so that you see exactly what have failed. And finally, I've added final pdf/div filename to be printed in the bash script on success.
            – jirislav
            Nov 11 at 16:34






            Thank you :) I've further improved the proposed answer so that it has disabled stdin when running pdflatex with : command, because it would seem to hang up when it prompts for input (grep doesn't print characters until newline is printed, so you can't possibly know what it's waiting for). Oh and I've found out that pdflatex always prints ! at the start of the line describing problem, so I've also updated the grep expression and added colored output so that you see exactly what have failed. And finally, I've added final pdf/div filename to be printed in the bash script on success.
            – jirislav
            Nov 11 at 16:34














            Would you like to submit it to CTAN?
            – egreg
            Nov 11 at 16:46




            Would you like to submit it to CTAN?
            – egreg
            Nov 11 at 16:46












            I've never submitted anything there until now :) .. I've called it pdfla­tex-quiet
            – jirislav
            Nov 11 at 17:30




            I've never submitted anything there until now :) .. I've called it pdfla­tex-quiet
            – jirislav
            Nov 11 at 17:30












            perhaps you could get in touch with Latexmk maintainer and suggest incorporation into it
            – jfbu
            Nov 12 at 22:31




            perhaps you could get in touch with Latexmk maintainer and suggest incorporation into it
            – jfbu
            Nov 12 at 22:31










            up vote
            3
            down vote













            FWIW, https://ctan.org/pkg/texfot was my attempt at solving this problem -- eliminating the verbose output from tex engines while still showing the interesting messages (the ones I actually want to do something about). --karl






            share|improve this answer

























              up vote
              3
              down vote













              FWIW, https://ctan.org/pkg/texfot was my attempt at solving this problem -- eliminating the verbose output from tex engines while still showing the interesting messages (the ones I actually want to do something about). --karl






              share|improve this answer























                up vote
                3
                down vote










                up vote
                3
                down vote









                FWIW, https://ctan.org/pkg/texfot was my attempt at solving this problem -- eliminating the verbose output from tex engines while still showing the interesting messages (the ones I actually want to do something about). --karl






                share|improve this answer












                FWIW, https://ctan.org/pkg/texfot was my attempt at solving this problem -- eliminating the verbose output from tex engines while still showing the interesting messages (the ones I actually want to do something about). --karl







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 12 at 22:13









                Karl Berry

                60173




                60173






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f166658%2fpdflatex-commandline-hide-compilation-output%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

                    How to change which sound is reproduced for terminal bell?

                    Can I use Tabulator js library in my java Spring + Thymeleaf project?

                    Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents