Avoid scrolling to document beginning on compiling?











up vote
0
down vote

favorite












Each time I compile Kile scrolls back to the beginning of the document. I would like to avoid this, it makes it very hard to write text as I need to browse back to the section I am editing each time. Any suggestions ?






compiling kile







share|improve this question
























  • Suggestion: If you're just editing text and aren't fine tuning placement of floats etc., just don't recompile so often. That's a bad habit anyway.
    – Skillmon
    yesterday










  • IF essential this may be possible if you are compiling to PDF (but NOT recommended, as you will see) 1) you will need to have an external pdf viewer outside your compile sequence but include synctex generation. 2) have a viewer that is able to reload itself on command. Now for your requirement, whilst you work you are halfway with some edits, you forward search to same PDF location in viewer & recompile As the link is broken tex goes to start and pdf is exactly as you left it. So you can inverse jump to previous point in tex. BUT tex and pdf are out of sync so you need to reopen pdf, not ideal
    – KJO
    14 hours ago










  • Just noticed a similar request here tex.stackexchange.com/questions/309942/… answer was to change call to okular and use F5
    – KJO
    13 hours ago










  • There are no such options in most (La)TeX compiler as I have known so far. However, if it is necessary that you have to compile very often and to keep the output in the same place, I suggest using Overleaf -- it does this very well as default. Anyway, I don't think that compiling too often is good.
    – Dũng Vũ
    7 hours ago










  • Also, if you are just editing text or picture, etc., as @Skillmon say, and not sure if the output is good (so you have to compile so often), I suggest you should make a new .tex file and copy all your text/pictures, which need editing, to the new file. The new file's output is only 1-2 pages long -- and it is very easy to scroll and find text in just 1-2 pages. When you see that the output is good enough, just copy the source code back from the new file to the original file and then just don't care about it anymore :)
    – Dũng Vũ
    7 hours ago















up vote
0
down vote

favorite












Each time I compile Kile scrolls back to the beginning of the document. I would like to avoid this, it makes it very hard to write text as I need to browse back to the section I am editing each time. Any suggestions ?






compiling kile







share|improve this question
























  • Suggestion: If you're just editing text and aren't fine tuning placement of floats etc., just don't recompile so often. That's a bad habit anyway.
    – Skillmon
    yesterday










  • IF essential this may be possible if you are compiling to PDF (but NOT recommended, as you will see) 1) you will need to have an external pdf viewer outside your compile sequence but include synctex generation. 2) have a viewer that is able to reload itself on command. Now for your requirement, whilst you work you are halfway with some edits, you forward search to same PDF location in viewer & recompile As the link is broken tex goes to start and pdf is exactly as you left it. So you can inverse jump to previous point in tex. BUT tex and pdf are out of sync so you need to reopen pdf, not ideal
    – KJO
    14 hours ago










  • Just noticed a similar request here tex.stackexchange.com/questions/309942/… answer was to change call to okular and use F5
    – KJO
    13 hours ago










  • There are no such options in most (La)TeX compiler as I have known so far. However, if it is necessary that you have to compile very often and to keep the output in the same place, I suggest using Overleaf -- it does this very well as default. Anyway, I don't think that compiling too often is good.
    – Dũng Vũ
    7 hours ago










  • Also, if you are just editing text or picture, etc., as @Skillmon say, and not sure if the output is good (so you have to compile so often), I suggest you should make a new .tex file and copy all your text/pictures, which need editing, to the new file. The new file's output is only 1-2 pages long -- and it is very easy to scroll and find text in just 1-2 pages. When you see that the output is good enough, just copy the source code back from the new file to the original file and then just don't care about it anymore :)
    – Dũng Vũ
    7 hours ago













up vote
0
down vote

favorite









up vote
0
down vote

favorite











Each time I compile Kile scrolls back to the beginning of the document. I would like to avoid this, it makes it very hard to write text as I need to browse back to the section I am editing each time. Any suggestions ?






compiling kile







share|improve this question















Each time I compile Kile scrolls back to the beginning of the document. I would like to avoid this, it makes it very hard to write text as I need to browse back to the section I am editing each time. Any suggestions ?






compiling kile




compiling kile






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 19 hours ago









Nicola Talbot

33.4k257104




33.4k257104










asked yesterday









Sulian thual-larrivé

11




11












  • Suggestion: If you're just editing text and aren't fine tuning placement of floats etc., just don't recompile so often. That's a bad habit anyway.
    – Skillmon
    yesterday










  • IF essential this may be possible if you are compiling to PDF (but NOT recommended, as you will see) 1) you will need to have an external pdf viewer outside your compile sequence but include synctex generation. 2) have a viewer that is able to reload itself on command. Now for your requirement, whilst you work you are halfway with some edits, you forward search to same PDF location in viewer & recompile As the link is broken tex goes to start and pdf is exactly as you left it. So you can inverse jump to previous point in tex. BUT tex and pdf are out of sync so you need to reopen pdf, not ideal
    – KJO
    14 hours ago










  • Just noticed a similar request here tex.stackexchange.com/questions/309942/… answer was to change call to okular and use F5
    – KJO
    13 hours ago










  • There are no such options in most (La)TeX compiler as I have known so far. However, if it is necessary that you have to compile very often and to keep the output in the same place, I suggest using Overleaf -- it does this very well as default. Anyway, I don't think that compiling too often is good.
    – Dũng Vũ
    7 hours ago










  • Also, if you are just editing text or picture, etc., as @Skillmon say, and not sure if the output is good (so you have to compile so often), I suggest you should make a new .tex file and copy all your text/pictures, which need editing, to the new file. The new file's output is only 1-2 pages long -- and it is very easy to scroll and find text in just 1-2 pages. When you see that the output is good enough, just copy the source code back from the new file to the original file and then just don't care about it anymore :)
    – Dũng Vũ
    7 hours ago


















  • Suggestion: If you're just editing text and aren't fine tuning placement of floats etc., just don't recompile so often. That's a bad habit anyway.
    – Skillmon
    yesterday










  • IF essential this may be possible if you are compiling to PDF (but NOT recommended, as you will see) 1) you will need to have an external pdf viewer outside your compile sequence but include synctex generation. 2) have a viewer that is able to reload itself on command. Now for your requirement, whilst you work you are halfway with some edits, you forward search to same PDF location in viewer & recompile As the link is broken tex goes to start and pdf is exactly as you left it. So you can inverse jump to previous point in tex. BUT tex and pdf are out of sync so you need to reopen pdf, not ideal
    – KJO
    14 hours ago










  • Just noticed a similar request here tex.stackexchange.com/questions/309942/… answer was to change call to okular and use F5
    – KJO
    13 hours ago










  • There are no such options in most (La)TeX compiler as I have known so far. However, if it is necessary that you have to compile very often and to keep the output in the same place, I suggest using Overleaf -- it does this very well as default. Anyway, I don't think that compiling too often is good.
    – Dũng Vũ
    7 hours ago










  • Also, if you are just editing text or picture, etc., as @Skillmon say, and not sure if the output is good (so you have to compile so often), I suggest you should make a new .tex file and copy all your text/pictures, which need editing, to the new file. The new file's output is only 1-2 pages long -- and it is very easy to scroll and find text in just 1-2 pages. When you see that the output is good enough, just copy the source code back from the new file to the original file and then just don't care about it anymore :)
    – Dũng Vũ
    7 hours ago
















Suggestion: If you're just editing text and aren't fine tuning placement of floats etc., just don't recompile so often. That's a bad habit anyway.
– Skillmon
yesterday




Suggestion: If you're just editing text and aren't fine tuning placement of floats etc., just don't recompile so often. That's a bad habit anyway.
– Skillmon
yesterday












IF essential this may be possible if you are compiling to PDF (but NOT recommended, as you will see) 1) you will need to have an external pdf viewer outside your compile sequence but include synctex generation. 2) have a viewer that is able to reload itself on command. Now for your requirement, whilst you work you are halfway with some edits, you forward search to same PDF location in viewer & recompile As the link is broken tex goes to start and pdf is exactly as you left it. So you can inverse jump to previous point in tex. BUT tex and pdf are out of sync so you need to reopen pdf, not ideal
– KJO
14 hours ago




IF essential this may be possible if you are compiling to PDF (but NOT recommended, as you will see) 1) you will need to have an external pdf viewer outside your compile sequence but include synctex generation. 2) have a viewer that is able to reload itself on command. Now for your requirement, whilst you work you are halfway with some edits, you forward search to same PDF location in viewer & recompile As the link is broken tex goes to start and pdf is exactly as you left it. So you can inverse jump to previous point in tex. BUT tex and pdf are out of sync so you need to reopen pdf, not ideal
– KJO
14 hours ago












Just noticed a similar request here tex.stackexchange.com/questions/309942/… answer was to change call to okular and use F5
– KJO
13 hours ago




Just noticed a similar request here tex.stackexchange.com/questions/309942/… answer was to change call to okular and use F5
– KJO
13 hours ago












There are no such options in most (La)TeX compiler as I have known so far. However, if it is necessary that you have to compile very often and to keep the output in the same place, I suggest using Overleaf -- it does this very well as default. Anyway, I don't think that compiling too often is good.
– Dũng Vũ
7 hours ago




There are no such options in most (La)TeX compiler as I have known so far. However, if it is necessary that you have to compile very often and to keep the output in the same place, I suggest using Overleaf -- it does this very well as default. Anyway, I don't think that compiling too often is good.
– Dũng Vũ
7 hours ago












Also, if you are just editing text or picture, etc., as @Skillmon say, and not sure if the output is good (so you have to compile so often), I suggest you should make a new .tex file and copy all your text/pictures, which need editing, to the new file. The new file's output is only 1-2 pages long -- and it is very easy to scroll and find text in just 1-2 pages. When you see that the output is good enough, just copy the source code back from the new file to the original file and then just don't care about it anymore :)
– Dũng Vũ
7 hours ago




Also, if you are just editing text or picture, etc., as @Skillmon say, and not sure if the output is good (so you have to compile so often), I suggest you should make a new .tex file and copy all your text/pictures, which need editing, to the new file. The new file's output is only 1-2 pages long -- and it is very easy to scroll and find text in just 1-2 pages. When you see that the output is good enough, just copy the source code back from the new file to the original file and then just don't care about it anymore :)
– Dũng Vũ
7 hours ago










1 Answer
1






active

oldest

votes

















up vote
0
down vote













When an error is encountered during the compilation, Kile opens the location of the first error. With some kinds of errors, Kile cannot determine where the error is located, and so it jumps to the beginning of the document. For example, this happens frequently with missing closing brackets.



The best thing is to investigate the error output (click on "Output" in the bottom menu and scroll until you find the error). When the output is long and/or you cannot find the error in it, run the compilation on command line (e.g. pdflatex my-document.tex or latex my-document.tex); the compilation will stop with a helpful message explaining where latex came to the conclusion that something is wrong, and if you investigate that spot in your input, you'll usually be able to correct it. (Press x on the command line to stop attempting further compilation after the first message.)



If you do not care to correct the compilation error (e.g., you have a coauthor who is much better than you at finding the problematic spot), then you can switch off the "Jump to first error" option. It's a tickbox in Kile's Settings > Configure Kile > Build > PDFLaTeX (the last part may be different; if you're compiling to DVI, it would be just LaTeX).






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%2f460109%2favoid-scrolling-to-document-beginning-on-compiling%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    When an error is encountered during the compilation, Kile opens the location of the first error. With some kinds of errors, Kile cannot determine where the error is located, and so it jumps to the beginning of the document. For example, this happens frequently with missing closing brackets.



    The best thing is to investigate the error output (click on "Output" in the bottom menu and scroll until you find the error). When the output is long and/or you cannot find the error in it, run the compilation on command line (e.g. pdflatex my-document.tex or latex my-document.tex); the compilation will stop with a helpful message explaining where latex came to the conclusion that something is wrong, and if you investigate that spot in your input, you'll usually be able to correct it. (Press x on the command line to stop attempting further compilation after the first message.)



    If you do not care to correct the compilation error (e.g., you have a coauthor who is much better than you at finding the problematic spot), then you can switch off the "Jump to first error" option. It's a tickbox in Kile's Settings > Configure Kile > Build > PDFLaTeX (the last part may be different; if you're compiling to DVI, it would be just LaTeX).






    share|improve this answer

























      up vote
      0
      down vote













      When an error is encountered during the compilation, Kile opens the location of the first error. With some kinds of errors, Kile cannot determine where the error is located, and so it jumps to the beginning of the document. For example, this happens frequently with missing closing brackets.



      The best thing is to investigate the error output (click on "Output" in the bottom menu and scroll until you find the error). When the output is long and/or you cannot find the error in it, run the compilation on command line (e.g. pdflatex my-document.tex or latex my-document.tex); the compilation will stop with a helpful message explaining where latex came to the conclusion that something is wrong, and if you investigate that spot in your input, you'll usually be able to correct it. (Press x on the command line to stop attempting further compilation after the first message.)



      If you do not care to correct the compilation error (e.g., you have a coauthor who is much better than you at finding the problematic spot), then you can switch off the "Jump to first error" option. It's a tickbox in Kile's Settings > Configure Kile > Build > PDFLaTeX (the last part may be different; if you're compiling to DVI, it would be just LaTeX).






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        When an error is encountered during the compilation, Kile opens the location of the first error. With some kinds of errors, Kile cannot determine where the error is located, and so it jumps to the beginning of the document. For example, this happens frequently with missing closing brackets.



        The best thing is to investigate the error output (click on "Output" in the bottom menu and scroll until you find the error). When the output is long and/or you cannot find the error in it, run the compilation on command line (e.g. pdflatex my-document.tex or latex my-document.tex); the compilation will stop with a helpful message explaining where latex came to the conclusion that something is wrong, and if you investigate that spot in your input, you'll usually be able to correct it. (Press x on the command line to stop attempting further compilation after the first message.)



        If you do not care to correct the compilation error (e.g., you have a coauthor who is much better than you at finding the problematic spot), then you can switch off the "Jump to first error" option. It's a tickbox in Kile's Settings > Configure Kile > Build > PDFLaTeX (the last part may be different; if you're compiling to DVI, it would be just LaTeX).






        share|improve this answer












        When an error is encountered during the compilation, Kile opens the location of the first error. With some kinds of errors, Kile cannot determine where the error is located, and so it jumps to the beginning of the document. For example, this happens frequently with missing closing brackets.



        The best thing is to investigate the error output (click on "Output" in the bottom menu and scroll until you find the error). When the output is long and/or you cannot find the error in it, run the compilation on command line (e.g. pdflatex my-document.tex or latex my-document.tex); the compilation will stop with a helpful message explaining where latex came to the conclusion that something is wrong, and if you investigate that spot in your input, you'll usually be able to correct it. (Press x on the command line to stop attempting further compilation after the first message.)



        If you do not care to correct the compilation error (e.g., you have a coauthor who is much better than you at finding the problematic spot), then you can switch off the "Jump to first error" option. It's a tickbox in Kile's Settings > Configure Kile > Build > PDFLaTeX (the last part may be different; if you're compiling to DVI, it would be just LaTeX).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 1 hour ago









        Ansa211

        1476




        1476






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f460109%2favoid-scrolling-to-document-beginning-on-compiling%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

            Accessing regular linux commands in Huawei's Dopra Linux

            Image
            4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel...
            Read more

            Can't connect RFCOMM socket: Host is down

            Image
            up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2 ...
            Read more

            Kernel panic - not syncing: Fatal Exception in Interrupt

            Image
            0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment ...
            Read more