hide console window in texshop
I like to work with the tex on one half of the screen and the pdf on the other.
How do I hide the console window (with transcription log, error report, etc) unless there is an error? And how can I keep the focus on the tex window?
That way, I command-T to see my pdf, but keep typing.
texshop
add a comment |
I like to work with the tex on one half of the screen and the pdf on the other.
How do I hide the console window (with transcription log, error report, etc) unless there is an error? And how can I keep the focus on the tex window?
That way, I command-T to see my pdf, but keep typing.
texshop
1
Welcome to TeX.sx!
– texenthusiast
Mar 4 '13 at 23:46
add a comment |
I like to work with the tex on one half of the screen and the pdf on the other.
How do I hide the console window (with transcription log, error report, etc) unless there is an error? And how can I keep the focus on the tex window?
That way, I command-T to see my pdf, but keep typing.
texshop
I like to work with the tex on one half of the screen and the pdf on the other.
How do I hide the console window (with transcription log, error report, etc) unless there is an error? And how can I keep the focus on the tex window?
That way, I command-T to see my pdf, but keep typing.
texshop
texshop
asked Mar 4 '13 at 23:40
sam boosalissam boosalis
13314
13314
1
Welcome to TeX.sx!
– texenthusiast
Mar 4 '13 at 23:46
add a comment |
1
Welcome to TeX.sx!
– texenthusiast
Mar 4 '13 at 23:46
1
1
Welcome to TeX.sx!
– texenthusiast
Mar 4 '13 at 23:46
Welcome to TeX.sx!
– texenthusiast
Mar 4 '13 at 23:46
add a comment |
3 Answers
3
active
oldest
votes
You can find options for those in the preferences:
- TeXShop, Preferences, choose tab "Console" and set "Show Console" to "when error occurs" (default is "always")
- TeXShop, Preferences, choose tab "Typesetting" and set "After Typesetting" to "continue editing" (default is "bring preview forward")
Is it possible to ignore warnings?
– Sibbs Gambling
Oct 26 '14 at 2:52
Neither of these work anymore on MacOS High Sierra (10.13) in full screen split mode. I'm beyond annoyed that the console sits permanently in front of the PDF.
– layman
May 16 '18 at 22:55
add a comment |
Currently I use macOS Mojave, v. 10.14. As addressed by @layman, the currently accepted answer no longer works (at least it did not work for me). The workaround I've used is the following:
- Open TexShop and compile your source.
- Take the console and place it in a non-bothersome position (this can be on a new desktop, your current desktop, etc... (I have yet to test if this works in a new window))
- Go to TexShop, Preferences, Console, and then select the option "All consoles start at a fixed position". This will allow you to let the console run, but do it in a fixed position away from where you are.
- After having done the above, click the "Set with current position" button. This will let your current non-obstructive placement of the console become the default placement.
- On the same page, select the "when error occurs" option. This stops TexShop from moving to the location of the console when there is not an error.
Each time you close TexShop, the current position of the console that you set will be forgotten. Simply place the console in the non-obstructive location again, and click the "Set with current position" button again under the console tab to reset this.
New contributor
add a comment |
I also encountered the bug on MacOS High Sierra (10.13) in full screen split mode.
It might help to drag the console window away as a separate window outside. And then switch to the full window in TexShop. When you click 'Typeset', the console shows the result like in backend, and you will not get bothered by the console window.
add a comment |
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
});
}
});
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%2f100936%2fhide-console-window-in-texshop%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
You can find options for those in the preferences:
- TeXShop, Preferences, choose tab "Console" and set "Show Console" to "when error occurs" (default is "always")
- TeXShop, Preferences, choose tab "Typesetting" and set "After Typesetting" to "continue editing" (default is "bring preview forward")
Is it possible to ignore warnings?
– Sibbs Gambling
Oct 26 '14 at 2:52
Neither of these work anymore on MacOS High Sierra (10.13) in full screen split mode. I'm beyond annoyed that the console sits permanently in front of the PDF.
– layman
May 16 '18 at 22:55
add a comment |
You can find options for those in the preferences:
- TeXShop, Preferences, choose tab "Console" and set "Show Console" to "when error occurs" (default is "always")
- TeXShop, Preferences, choose tab "Typesetting" and set "After Typesetting" to "continue editing" (default is "bring preview forward")
Is it possible to ignore warnings?
– Sibbs Gambling
Oct 26 '14 at 2:52
Neither of these work anymore on MacOS High Sierra (10.13) in full screen split mode. I'm beyond annoyed that the console sits permanently in front of the PDF.
– layman
May 16 '18 at 22:55
add a comment |
You can find options for those in the preferences:
- TeXShop, Preferences, choose tab "Console" and set "Show Console" to "when error occurs" (default is "always")
- TeXShop, Preferences, choose tab "Typesetting" and set "After Typesetting" to "continue editing" (default is "bring preview forward")
You can find options for those in the preferences:
- TeXShop, Preferences, choose tab "Console" and set "Show Console" to "when error occurs" (default is "always")
- TeXShop, Preferences, choose tab "Typesetting" and set "After Typesetting" to "continue editing" (default is "bring preview forward")
answered Mar 4 '13 at 23:48
user26372user26372
1,2101120
1,2101120
Is it possible to ignore warnings?
– Sibbs Gambling
Oct 26 '14 at 2:52
Neither of these work anymore on MacOS High Sierra (10.13) in full screen split mode. I'm beyond annoyed that the console sits permanently in front of the PDF.
– layman
May 16 '18 at 22:55
add a comment |
Is it possible to ignore warnings?
– Sibbs Gambling
Oct 26 '14 at 2:52
Neither of these work anymore on MacOS High Sierra (10.13) in full screen split mode. I'm beyond annoyed that the console sits permanently in front of the PDF.
– layman
May 16 '18 at 22:55
Is it possible to ignore warnings?
– Sibbs Gambling
Oct 26 '14 at 2:52
Is it possible to ignore warnings?
– Sibbs Gambling
Oct 26 '14 at 2:52
Neither of these work anymore on MacOS High Sierra (10.13) in full screen split mode. I'm beyond annoyed that the console sits permanently in front of the PDF.
– layman
May 16 '18 at 22:55
Neither of these work anymore on MacOS High Sierra (10.13) in full screen split mode. I'm beyond annoyed that the console sits permanently in front of the PDF.
– layman
May 16 '18 at 22:55
add a comment |
Currently I use macOS Mojave, v. 10.14. As addressed by @layman, the currently accepted answer no longer works (at least it did not work for me). The workaround I've used is the following:
- Open TexShop and compile your source.
- Take the console and place it in a non-bothersome position (this can be on a new desktop, your current desktop, etc... (I have yet to test if this works in a new window))
- Go to TexShop, Preferences, Console, and then select the option "All consoles start at a fixed position". This will allow you to let the console run, but do it in a fixed position away from where you are.
- After having done the above, click the "Set with current position" button. This will let your current non-obstructive placement of the console become the default placement.
- On the same page, select the "when error occurs" option. This stops TexShop from moving to the location of the console when there is not an error.
Each time you close TexShop, the current position of the console that you set will be forgotten. Simply place the console in the non-obstructive location again, and click the "Set with current position" button again under the console tab to reset this.
New contributor
add a comment |
Currently I use macOS Mojave, v. 10.14. As addressed by @layman, the currently accepted answer no longer works (at least it did not work for me). The workaround I've used is the following:
- Open TexShop and compile your source.
- Take the console and place it in a non-bothersome position (this can be on a new desktop, your current desktop, etc... (I have yet to test if this works in a new window))
- Go to TexShop, Preferences, Console, and then select the option "All consoles start at a fixed position". This will allow you to let the console run, but do it in a fixed position away from where you are.
- After having done the above, click the "Set with current position" button. This will let your current non-obstructive placement of the console become the default placement.
- On the same page, select the "when error occurs" option. This stops TexShop from moving to the location of the console when there is not an error.
Each time you close TexShop, the current position of the console that you set will be forgotten. Simply place the console in the non-obstructive location again, and click the "Set with current position" button again under the console tab to reset this.
New contributor
add a comment |
Currently I use macOS Mojave, v. 10.14. As addressed by @layman, the currently accepted answer no longer works (at least it did not work for me). The workaround I've used is the following:
- Open TexShop and compile your source.
- Take the console and place it in a non-bothersome position (this can be on a new desktop, your current desktop, etc... (I have yet to test if this works in a new window))
- Go to TexShop, Preferences, Console, and then select the option "All consoles start at a fixed position". This will allow you to let the console run, but do it in a fixed position away from where you are.
- After having done the above, click the "Set with current position" button. This will let your current non-obstructive placement of the console become the default placement.
- On the same page, select the "when error occurs" option. This stops TexShop from moving to the location of the console when there is not an error.
Each time you close TexShop, the current position of the console that you set will be forgotten. Simply place the console in the non-obstructive location again, and click the "Set with current position" button again under the console tab to reset this.
New contributor
Currently I use macOS Mojave, v. 10.14. As addressed by @layman, the currently accepted answer no longer works (at least it did not work for me). The workaround I've used is the following:
- Open TexShop and compile your source.
- Take the console and place it in a non-bothersome position (this can be on a new desktop, your current desktop, etc... (I have yet to test if this works in a new window))
- Go to TexShop, Preferences, Console, and then select the option "All consoles start at a fixed position". This will allow you to let the console run, but do it in a fixed position away from where you are.
- After having done the above, click the "Set with current position" button. This will let your current non-obstructive placement of the console become the default placement.
- On the same page, select the "when error occurs" option. This stops TexShop from moving to the location of the console when there is not an error.
Each time you close TexShop, the current position of the console that you set will be forgotten. Simply place the console in the non-obstructive location again, and click the "Set with current position" button again under the console tab to reset this.
New contributor
New contributor
answered 3 mins ago
SethSeth
11
11
New contributor
New contributor
add a comment |
add a comment |
I also encountered the bug on MacOS High Sierra (10.13) in full screen split mode.
It might help to drag the console window away as a separate window outside. And then switch to the full window in TexShop. When you click 'Typeset', the console shows the result like in backend, and you will not get bothered by the console window.
add a comment |
I also encountered the bug on MacOS High Sierra (10.13) in full screen split mode.
It might help to drag the console window away as a separate window outside. And then switch to the full window in TexShop. When you click 'Typeset', the console shows the result like in backend, and you will not get bothered by the console window.
add a comment |
I also encountered the bug on MacOS High Sierra (10.13) in full screen split mode.
It might help to drag the console window away as a separate window outside. And then switch to the full window in TexShop. When you click 'Typeset', the console shows the result like in backend, and you will not get bothered by the console window.
I also encountered the bug on MacOS High Sierra (10.13) in full screen split mode.
It might help to drag the console window away as a separate window outside. And then switch to the full window in TexShop. When you click 'Typeset', the console shows the result like in backend, and you will not get bothered by the console window.
answered Oct 15 '18 at 16:11
刘伟麟刘伟麟
1
1
add a comment |
add a comment |
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.
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%2f100936%2fhide-console-window-in-texshop%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
1
Welcome to TeX.sx!
– texenthusiast
Mar 4 '13 at 23:46