TeXstudio generates “plain text” when using Build&View (Debian+XFCE)












0















I saw this closed question and I'm experienceing something similar: for .tex documents, when I press the f5 key, which triggers the macro "Build and view", I get an output .pdf file that is treated by Thunar as a "plain text" file; I doulbe-click on it and the text editor is executed. I use the embedded pdf viewer in TeXstudio.



Running pdflatex on a terminal or using another editor, the problem doesn't occur; even on TeXstudio, if I only use the Build macro and then the view command, I get a proper .pdf file.



I even ran the Build > View on the following file:



    documentclass{article}

usepackage{lipsum}

begin{document}
lipsum
end{document}


The Build > View command produced a proper PDF from the above.



Any ideas on how to know what is going on? Thank you!










share|improve this question





























    0















    I saw this closed question and I'm experienceing something similar: for .tex documents, when I press the f5 key, which triggers the macro "Build and view", I get an output .pdf file that is treated by Thunar as a "plain text" file; I doulbe-click on it and the text editor is executed. I use the embedded pdf viewer in TeXstudio.



    Running pdflatex on a terminal or using another editor, the problem doesn't occur; even on TeXstudio, if I only use the Build macro and then the view command, I get a proper .pdf file.



    I even ran the Build > View on the following file:



        documentclass{article}

    usepackage{lipsum}

    begin{document}
    lipsum
    end{document}


    The Build > View command produced a proper PDF from the above.



    Any ideas on how to know what is going on? Thank you!










    share|improve this question



























      0












      0








      0








      I saw this closed question and I'm experienceing something similar: for .tex documents, when I press the f5 key, which triggers the macro "Build and view", I get an output .pdf file that is treated by Thunar as a "plain text" file; I doulbe-click on it and the text editor is executed. I use the embedded pdf viewer in TeXstudio.



      Running pdflatex on a terminal or using another editor, the problem doesn't occur; even on TeXstudio, if I only use the Build macro and then the view command, I get a proper .pdf file.



      I even ran the Build > View on the following file:



          documentclass{article}

      usepackage{lipsum}

      begin{document}
      lipsum
      end{document}


      The Build > View command produced a proper PDF from the above.



      Any ideas on how to know what is going on? Thank you!










      share|improve this question
















      I saw this closed question and I'm experienceing something similar: for .tex documents, when I press the f5 key, which triggers the macro "Build and view", I get an output .pdf file that is treated by Thunar as a "plain text" file; I doulbe-click on it and the text editor is executed. I use the embedded pdf viewer in TeXstudio.



      Running pdflatex on a terminal or using another editor, the problem doesn't occur; even on TeXstudio, if I only use the Build macro and then the view command, I get a proper .pdf file.



      I even ran the Build > View on the following file:



          documentclass{article}

      usepackage{lipsum}

      begin{document}
      lipsum
      end{document}


      The Build > View command produced a proper PDF from the above.



      Any ideas on how to know what is going on? Thank you!







      theorems texstudio






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 24 mins ago







      Óscar Guajardo

















      asked Feb 4 at 19:13









      Óscar GuajardoÓscar Guajardo

      199110




      199110






















          2 Answers
          2






          active

          oldest

          votes


















          0














          F5 is the default shortcut for Build & View, check if this is your current shortcut in Options/Configure TeXstudio.../Shortcuts/Menus/Tools.



          Build & View is defined in Options/Configure TeXstudio.../Build/Build & View. Please check the value of this. The default value is txs:///compile | txs:///view. If this is different, please set it back to that.



          txs:///compile is defined just below Build & View, please check that the value is txs:///pdflatex



          txs:///pdflatex is defined in Options/Configure TeXstudio.../Commands/PdfLaTeX and the default value is pdflatex -synctex=1 -interaction=nonstopmode %.tex. If this is different, please set it back to that.



          If this does not solve, could you describe some more the "plain-text .pdf file" contents?






          share|improve this answer








          New contributor




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





















          • The configuration is as you describe it. I cannot tell you about the contents of the file because when trying to open it (on Mousepad, in my case) I get a window with the error "The document was not UTF-8 valid"; changing the encoding doesn't allow me to open it either. However, in trying to get into the contents, I typed on terminal cat output.pdf > output2.pdf (just as an example) and this produced a proper PDF file. Again, the faulted PDF is produced only when I run Build & View.

            – Óscar Guajardo
            Feb 6 at 2:10













          • I can't understand how this could happen, there seems to be a problem with TeXstudio as one button works and the other doesn't and there seems to be a problem with your Debian deciding that two seemingly identical (cat just identically copies the content from one file to the other, no modification of the content, just the creation date, the permissions and other non-important things will be different) files should be opened in two different ways. Can you share the faulty pdf?

            – Ilario Gelmetti
            Feb 6 at 10:21











          • I was about to share the file but I started experimenting; I had defined a 'theorem' for Remarks, and I named it rem; it was this that was causing trouble; I just renamed it and everything works fine! Apparently rem is some sort of internal command for TeXstudio: sourceforge.net/p/texstudio/discussion/907839/thread/09d48286 Thanks for the interest! :)

            – Óscar Guajardo
            Feb 6 at 17:48













          • This is weird... Maybe it's a TeXstudio bug or something like that. If you can provide a MWE with this behaviour it would be interesting. Just adding that newtheorem in a document of mine is not enough for reproducing the weird behaviour.

            – Ilario Gelmetti
            Feb 7 at 15:40











          • What version of TeXstudio do you use? Mine is 2.12.14 from the Debian testing repos.

            – Óscar Guajardo
            Feb 7 at 18:17





















          0














          Apparently the problem was an environment whose call word was rem (I used it to define a Remark 'theorem': newtheorem{rem}{Remark}). I just renamed it and now running Build&View produces a true PDF file.






          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%2f473363%2ftexstudio-generates-plain-text-when-using-buildview-debianxfce%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









            0














            F5 is the default shortcut for Build & View, check if this is your current shortcut in Options/Configure TeXstudio.../Shortcuts/Menus/Tools.



            Build & View is defined in Options/Configure TeXstudio.../Build/Build & View. Please check the value of this. The default value is txs:///compile | txs:///view. If this is different, please set it back to that.



            txs:///compile is defined just below Build & View, please check that the value is txs:///pdflatex



            txs:///pdflatex is defined in Options/Configure TeXstudio.../Commands/PdfLaTeX and the default value is pdflatex -synctex=1 -interaction=nonstopmode %.tex. If this is different, please set it back to that.



            If this does not solve, could you describe some more the "plain-text .pdf file" contents?






            share|improve this answer








            New contributor




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





















            • The configuration is as you describe it. I cannot tell you about the contents of the file because when trying to open it (on Mousepad, in my case) I get a window with the error "The document was not UTF-8 valid"; changing the encoding doesn't allow me to open it either. However, in trying to get into the contents, I typed on terminal cat output.pdf > output2.pdf (just as an example) and this produced a proper PDF file. Again, the faulted PDF is produced only when I run Build & View.

              – Óscar Guajardo
              Feb 6 at 2:10













            • I can't understand how this could happen, there seems to be a problem with TeXstudio as one button works and the other doesn't and there seems to be a problem with your Debian deciding that two seemingly identical (cat just identically copies the content from one file to the other, no modification of the content, just the creation date, the permissions and other non-important things will be different) files should be opened in two different ways. Can you share the faulty pdf?

              – Ilario Gelmetti
              Feb 6 at 10:21











            • I was about to share the file but I started experimenting; I had defined a 'theorem' for Remarks, and I named it rem; it was this that was causing trouble; I just renamed it and everything works fine! Apparently rem is some sort of internal command for TeXstudio: sourceforge.net/p/texstudio/discussion/907839/thread/09d48286 Thanks for the interest! :)

              – Óscar Guajardo
              Feb 6 at 17:48













            • This is weird... Maybe it's a TeXstudio bug or something like that. If you can provide a MWE with this behaviour it would be interesting. Just adding that newtheorem in a document of mine is not enough for reproducing the weird behaviour.

              – Ilario Gelmetti
              Feb 7 at 15:40











            • What version of TeXstudio do you use? Mine is 2.12.14 from the Debian testing repos.

              – Óscar Guajardo
              Feb 7 at 18:17


















            0














            F5 is the default shortcut for Build & View, check if this is your current shortcut in Options/Configure TeXstudio.../Shortcuts/Menus/Tools.



            Build & View is defined in Options/Configure TeXstudio.../Build/Build & View. Please check the value of this. The default value is txs:///compile | txs:///view. If this is different, please set it back to that.



            txs:///compile is defined just below Build & View, please check that the value is txs:///pdflatex



            txs:///pdflatex is defined in Options/Configure TeXstudio.../Commands/PdfLaTeX and the default value is pdflatex -synctex=1 -interaction=nonstopmode %.tex. If this is different, please set it back to that.



            If this does not solve, could you describe some more the "plain-text .pdf file" contents?






            share|improve this answer








            New contributor




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





















            • The configuration is as you describe it. I cannot tell you about the contents of the file because when trying to open it (on Mousepad, in my case) I get a window with the error "The document was not UTF-8 valid"; changing the encoding doesn't allow me to open it either. However, in trying to get into the contents, I typed on terminal cat output.pdf > output2.pdf (just as an example) and this produced a proper PDF file. Again, the faulted PDF is produced only when I run Build & View.

              – Óscar Guajardo
              Feb 6 at 2:10













            • I can't understand how this could happen, there seems to be a problem with TeXstudio as one button works and the other doesn't and there seems to be a problem with your Debian deciding that two seemingly identical (cat just identically copies the content from one file to the other, no modification of the content, just the creation date, the permissions and other non-important things will be different) files should be opened in two different ways. Can you share the faulty pdf?

              – Ilario Gelmetti
              Feb 6 at 10:21











            • I was about to share the file but I started experimenting; I had defined a 'theorem' for Remarks, and I named it rem; it was this that was causing trouble; I just renamed it and everything works fine! Apparently rem is some sort of internal command for TeXstudio: sourceforge.net/p/texstudio/discussion/907839/thread/09d48286 Thanks for the interest! :)

              – Óscar Guajardo
              Feb 6 at 17:48













            • This is weird... Maybe it's a TeXstudio bug or something like that. If you can provide a MWE with this behaviour it would be interesting. Just adding that newtheorem in a document of mine is not enough for reproducing the weird behaviour.

              – Ilario Gelmetti
              Feb 7 at 15:40











            • What version of TeXstudio do you use? Mine is 2.12.14 from the Debian testing repos.

              – Óscar Guajardo
              Feb 7 at 18:17
















            0












            0








            0







            F5 is the default shortcut for Build & View, check if this is your current shortcut in Options/Configure TeXstudio.../Shortcuts/Menus/Tools.



            Build & View is defined in Options/Configure TeXstudio.../Build/Build & View. Please check the value of this. The default value is txs:///compile | txs:///view. If this is different, please set it back to that.



            txs:///compile is defined just below Build & View, please check that the value is txs:///pdflatex



            txs:///pdflatex is defined in Options/Configure TeXstudio.../Commands/PdfLaTeX and the default value is pdflatex -synctex=1 -interaction=nonstopmode %.tex. If this is different, please set it back to that.



            If this does not solve, could you describe some more the "plain-text .pdf file" contents?






            share|improve this answer








            New contributor




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










            F5 is the default shortcut for Build & View, check if this is your current shortcut in Options/Configure TeXstudio.../Shortcuts/Menus/Tools.



            Build & View is defined in Options/Configure TeXstudio.../Build/Build & View. Please check the value of this. The default value is txs:///compile | txs:///view. If this is different, please set it back to that.



            txs:///compile is defined just below Build & View, please check that the value is txs:///pdflatex



            txs:///pdflatex is defined in Options/Configure TeXstudio.../Commands/PdfLaTeX and the default value is pdflatex -synctex=1 -interaction=nonstopmode %.tex. If this is different, please set it back to that.



            If this does not solve, could you describe some more the "plain-text .pdf file" contents?







            share|improve this answer








            New contributor




            Ilario Gelmetti 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






            New contributor




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









            answered Feb 5 at 16:10









            Ilario GelmettiIlario Gelmetti

            11




            11




            New contributor




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





            New contributor





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






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













            • The configuration is as you describe it. I cannot tell you about the contents of the file because when trying to open it (on Mousepad, in my case) I get a window with the error "The document was not UTF-8 valid"; changing the encoding doesn't allow me to open it either. However, in trying to get into the contents, I typed on terminal cat output.pdf > output2.pdf (just as an example) and this produced a proper PDF file. Again, the faulted PDF is produced only when I run Build & View.

              – Óscar Guajardo
              Feb 6 at 2:10













            • I can't understand how this could happen, there seems to be a problem with TeXstudio as one button works and the other doesn't and there seems to be a problem with your Debian deciding that two seemingly identical (cat just identically copies the content from one file to the other, no modification of the content, just the creation date, the permissions and other non-important things will be different) files should be opened in two different ways. Can you share the faulty pdf?

              – Ilario Gelmetti
              Feb 6 at 10:21











            • I was about to share the file but I started experimenting; I had defined a 'theorem' for Remarks, and I named it rem; it was this that was causing trouble; I just renamed it and everything works fine! Apparently rem is some sort of internal command for TeXstudio: sourceforge.net/p/texstudio/discussion/907839/thread/09d48286 Thanks for the interest! :)

              – Óscar Guajardo
              Feb 6 at 17:48













            • This is weird... Maybe it's a TeXstudio bug or something like that. If you can provide a MWE with this behaviour it would be interesting. Just adding that newtheorem in a document of mine is not enough for reproducing the weird behaviour.

              – Ilario Gelmetti
              Feb 7 at 15:40











            • What version of TeXstudio do you use? Mine is 2.12.14 from the Debian testing repos.

              – Óscar Guajardo
              Feb 7 at 18:17





















            • The configuration is as you describe it. I cannot tell you about the contents of the file because when trying to open it (on Mousepad, in my case) I get a window with the error "The document was not UTF-8 valid"; changing the encoding doesn't allow me to open it either. However, in trying to get into the contents, I typed on terminal cat output.pdf > output2.pdf (just as an example) and this produced a proper PDF file. Again, the faulted PDF is produced only when I run Build & View.

              – Óscar Guajardo
              Feb 6 at 2:10













            • I can't understand how this could happen, there seems to be a problem with TeXstudio as one button works and the other doesn't and there seems to be a problem with your Debian deciding that two seemingly identical (cat just identically copies the content from one file to the other, no modification of the content, just the creation date, the permissions and other non-important things will be different) files should be opened in two different ways. Can you share the faulty pdf?

              – Ilario Gelmetti
              Feb 6 at 10:21











            • I was about to share the file but I started experimenting; I had defined a 'theorem' for Remarks, and I named it rem; it was this that was causing trouble; I just renamed it and everything works fine! Apparently rem is some sort of internal command for TeXstudio: sourceforge.net/p/texstudio/discussion/907839/thread/09d48286 Thanks for the interest! :)

              – Óscar Guajardo
              Feb 6 at 17:48













            • This is weird... Maybe it's a TeXstudio bug or something like that. If you can provide a MWE with this behaviour it would be interesting. Just adding that newtheorem in a document of mine is not enough for reproducing the weird behaviour.

              – Ilario Gelmetti
              Feb 7 at 15:40











            • What version of TeXstudio do you use? Mine is 2.12.14 from the Debian testing repos.

              – Óscar Guajardo
              Feb 7 at 18:17



















            The configuration is as you describe it. I cannot tell you about the contents of the file because when trying to open it (on Mousepad, in my case) I get a window with the error "The document was not UTF-8 valid"; changing the encoding doesn't allow me to open it either. However, in trying to get into the contents, I typed on terminal cat output.pdf > output2.pdf (just as an example) and this produced a proper PDF file. Again, the faulted PDF is produced only when I run Build & View.

            – Óscar Guajardo
            Feb 6 at 2:10







            The configuration is as you describe it. I cannot tell you about the contents of the file because when trying to open it (on Mousepad, in my case) I get a window with the error "The document was not UTF-8 valid"; changing the encoding doesn't allow me to open it either. However, in trying to get into the contents, I typed on terminal cat output.pdf > output2.pdf (just as an example) and this produced a proper PDF file. Again, the faulted PDF is produced only when I run Build & View.

            – Óscar Guajardo
            Feb 6 at 2:10















            I can't understand how this could happen, there seems to be a problem with TeXstudio as one button works and the other doesn't and there seems to be a problem with your Debian deciding that two seemingly identical (cat just identically copies the content from one file to the other, no modification of the content, just the creation date, the permissions and other non-important things will be different) files should be opened in two different ways. Can you share the faulty pdf?

            – Ilario Gelmetti
            Feb 6 at 10:21





            I can't understand how this could happen, there seems to be a problem with TeXstudio as one button works and the other doesn't and there seems to be a problem with your Debian deciding that two seemingly identical (cat just identically copies the content from one file to the other, no modification of the content, just the creation date, the permissions and other non-important things will be different) files should be opened in two different ways. Can you share the faulty pdf?

            – Ilario Gelmetti
            Feb 6 at 10:21













            I was about to share the file but I started experimenting; I had defined a 'theorem' for Remarks, and I named it rem; it was this that was causing trouble; I just renamed it and everything works fine! Apparently rem is some sort of internal command for TeXstudio: sourceforge.net/p/texstudio/discussion/907839/thread/09d48286 Thanks for the interest! :)

            – Óscar Guajardo
            Feb 6 at 17:48







            I was about to share the file but I started experimenting; I had defined a 'theorem' for Remarks, and I named it rem; it was this that was causing trouble; I just renamed it and everything works fine! Apparently rem is some sort of internal command for TeXstudio: sourceforge.net/p/texstudio/discussion/907839/thread/09d48286 Thanks for the interest! :)

            – Óscar Guajardo
            Feb 6 at 17:48















            This is weird... Maybe it's a TeXstudio bug or something like that. If you can provide a MWE with this behaviour it would be interesting. Just adding that newtheorem in a document of mine is not enough for reproducing the weird behaviour.

            – Ilario Gelmetti
            Feb 7 at 15:40





            This is weird... Maybe it's a TeXstudio bug or something like that. If you can provide a MWE with this behaviour it would be interesting. Just adding that newtheorem in a document of mine is not enough for reproducing the weird behaviour.

            – Ilario Gelmetti
            Feb 7 at 15:40













            What version of TeXstudio do you use? Mine is 2.12.14 from the Debian testing repos.

            – Óscar Guajardo
            Feb 7 at 18:17







            What version of TeXstudio do you use? Mine is 2.12.14 from the Debian testing repos.

            – Óscar Guajardo
            Feb 7 at 18:17













            0














            Apparently the problem was an environment whose call word was rem (I used it to define a Remark 'theorem': newtheorem{rem}{Remark}). I just renamed it and now running Build&View produces a true PDF file.






            share|improve this answer




























              0














              Apparently the problem was an environment whose call word was rem (I used it to define a Remark 'theorem': newtheorem{rem}{Remark}). I just renamed it and now running Build&View produces a true PDF file.






              share|improve this answer


























                0












                0








                0







                Apparently the problem was an environment whose call word was rem (I used it to define a Remark 'theorem': newtheorem{rem}{Remark}). I just renamed it and now running Build&View produces a true PDF file.






                share|improve this answer













                Apparently the problem was an environment whose call word was rem (I used it to define a Remark 'theorem': newtheorem{rem}{Remark}). I just renamed it and now running Build&View produces a true PDF file.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 6 at 17:50









                Óscar GuajardoÓscar Guajardo

                199110




                199110






























                    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%2f473363%2ftexstudio-generates-plain-text-when-using-buildview-debianxfce%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

                    Lallio

                    Futebolista

                    Jornalista