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
edited 19 hours ago
Nicola Talbot
33.4k257104
asked yesterday
Sulian thual-larrivé
11
add a comment |
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
edited 19 hours ago
Nicola Talbot
33.4k257104
asked yesterday
Sulian thual-larrivé
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.texfile 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
add a comment |
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
edited 19 hours ago
Nicola Talbot
33.4k257104
asked yesterday
Sulian thual-larrivé
11
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
edited 19 hours ago
Nicola Talbot
33.4k257104
asked yesterday
Sulian thual-larrivé
11
edited 19 hours ago
Nicola Talbot
33.4k257104
asked yesterday
Sulian thual-larrivé
11
edited 19 hours ago
Nicola Talbot
33.4k257104
edited 19 hours ago
Nicola Talbot
33.4k257104
edited 19 hours ago
Nicola Talbot
33.4k257104
33.4k257104
asked yesterday
Sulian thual-larrivé
11
asked yesterday
Sulian thual-larrivé
11
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.texfile 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
add a comment |
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.texfile 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
add a comment |
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).
answered 1 hour ago
Ansa211
1476
add a comment |
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).
answered 1 hour ago
Ansa211
1476
add a comment |
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).
answered 1 hour ago
Ansa211
1476
add a comment |
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).
answered 1 hour ago
Ansa211
1476
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).
answered 1 hour ago
Ansa211
1476
answered 1 hour ago
Ansa211
1476
answered 1 hour ago
Ansa211
1476
answered 1 hour ago
Ansa211
1476
1476
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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
.texfile 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