MobaXterm: How to see previous commands' terminal output while still being in VIM? (Equivalent of 'Shift + Page Up' in PuTTY)
Clash Royale CLAN TAG#URR8PPP
What I want (which is possible in PuTTY):
1) Login to a machine (using PuTTY)
2) $ cat /some/file
[contents of the /some/file shown on screen]
3) $ vim
4) Press Shift + Page Up
Result: I can see [contents of the /some/file ] and everything else that was shown on the screen before I entered vim
.
Now if I try the same thing in Mobaxterm, which is another terminal application on Windows, I don't get to see the output of the previous commands; it only scrolls the file that I opened in vim
which is not what I want.
I tried to echo $TERM
from both PuTTY and Mobaxterm, and they both show xterm
as the output, so I'm not sure what's different in PuTTY.
terminal keyboard-shortcuts putty mobaxterm
add a comment |
What I want (which is possible in PuTTY):
1) Login to a machine (using PuTTY)
2) $ cat /some/file
[contents of the /some/file shown on screen]
3) $ vim
4) Press Shift + Page Up
Result: I can see [contents of the /some/file ] and everything else that was shown on the screen before I entered vim
.
Now if I try the same thing in Mobaxterm, which is another terminal application on Windows, I don't get to see the output of the previous commands; it only scrolls the file that I opened in vim
which is not what I want.
I tried to echo $TERM
from both PuTTY and Mobaxterm, and they both show xterm
as the output, so I'm not sure what's different in PuTTY.
terminal keyboard-shortcuts putty mobaxterm
Can someone please add mobaxterm to the list of tags? It seems I need 300+ points for it.
– Srikanth
Jul 7 '15 at 13:33
add a comment |
What I want (which is possible in PuTTY):
1) Login to a machine (using PuTTY)
2) $ cat /some/file
[contents of the /some/file shown on screen]
3) $ vim
4) Press Shift + Page Up
Result: I can see [contents of the /some/file ] and everything else that was shown on the screen before I entered vim
.
Now if I try the same thing in Mobaxterm, which is another terminal application on Windows, I don't get to see the output of the previous commands; it only scrolls the file that I opened in vim
which is not what I want.
I tried to echo $TERM
from both PuTTY and Mobaxterm, and they both show xterm
as the output, so I'm not sure what's different in PuTTY.
terminal keyboard-shortcuts putty mobaxterm
What I want (which is possible in PuTTY):
1) Login to a machine (using PuTTY)
2) $ cat /some/file
[contents of the /some/file shown on screen]
3) $ vim
4) Press Shift + Page Up
Result: I can see [contents of the /some/file ] and everything else that was shown on the screen before I entered vim
.
Now if I try the same thing in Mobaxterm, which is another terminal application on Windows, I don't get to see the output of the previous commands; it only scrolls the file that I opened in vim
which is not what I want.
I tried to echo $TERM
from both PuTTY and Mobaxterm, and they both show xterm
as the output, so I'm not sure what's different in PuTTY.
terminal keyboard-shortcuts putty mobaxterm
terminal keyboard-shortcuts putty mobaxterm
edited Jan 13 at 21:46
Rui F Ribeiro
39.7k1479132
39.7k1479132
asked Jul 7 '15 at 13:33
SrikanthSrikanth
10615
10615
Can someone please add mobaxterm to the list of tags? It seems I need 300+ points for it.
– Srikanth
Jul 7 '15 at 13:33
add a comment |
Can someone please add mobaxterm to the list of tags? It seems I need 300+ points for it.
– Srikanth
Jul 7 '15 at 13:33
Can someone please add mobaxterm to the list of tags? It seems I need 300+ points for it.
– Srikanth
Jul 7 '15 at 13:33
Can someone please add mobaxterm to the list of tags? It seems I need 300+ points for it.
– Srikanth
Jul 7 '15 at 13:33
add a comment |
2 Answers
2
active
oldest
votes
A simple solution is to suspend the running command, usually by typing control-Z
. You should then be back in the shell. Give the fg
command to return and bring the command back to the foreground again.
I've had bad experiences when doing this. My advice: Never background Vim; just use:shell
.
– Wildcard
Feb 15 '16 at 7:37
add a comment |
I think that another way is to send the command ":!" to vim. Then, you will view back the terminal, and would be able to see previous commands, until you type "enter" or a new VIM command. Then vim would come back.
Enjoy !
Gilles.
Or just run:shell
, which is more readable. Are those equivalent?
– Wildcard
Feb 15 '16 at 7:35
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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%2funix.stackexchange.com%2fquestions%2f214379%2fmobaxterm-how-to-see-previous-commands-terminal-output-while-still-being-in-vi%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
A simple solution is to suspend the running command, usually by typing control-Z
. You should then be back in the shell. Give the fg
command to return and bring the command back to the foreground again.
I've had bad experiences when doing this. My advice: Never background Vim; just use:shell
.
– Wildcard
Feb 15 '16 at 7:37
add a comment |
A simple solution is to suspend the running command, usually by typing control-Z
. You should then be back in the shell. Give the fg
command to return and bring the command back to the foreground again.
I've had bad experiences when doing this. My advice: Never background Vim; just use:shell
.
– Wildcard
Feb 15 '16 at 7:37
add a comment |
A simple solution is to suspend the running command, usually by typing control-Z
. You should then be back in the shell. Give the fg
command to return and bring the command back to the foreground again.
A simple solution is to suspend the running command, usually by typing control-Z
. You should then be back in the shell. Give the fg
command to return and bring the command back to the foreground again.
answered Jul 7 '15 at 13:47
meuhmeuh
31.9k11954
31.9k11954
I've had bad experiences when doing this. My advice: Never background Vim; just use:shell
.
– Wildcard
Feb 15 '16 at 7:37
add a comment |
I've had bad experiences when doing this. My advice: Never background Vim; just use:shell
.
– Wildcard
Feb 15 '16 at 7:37
I've had bad experiences when doing this. My advice: Never background Vim; just use
:shell
.– Wildcard
Feb 15 '16 at 7:37
I've had bad experiences when doing this. My advice: Never background Vim; just use
:shell
.– Wildcard
Feb 15 '16 at 7:37
add a comment |
I think that another way is to send the command ":!" to vim. Then, you will view back the terminal, and would be able to see previous commands, until you type "enter" or a new VIM command. Then vim would come back.
Enjoy !
Gilles.
Or just run:shell
, which is more readable. Are those equivalent?
– Wildcard
Feb 15 '16 at 7:35
add a comment |
I think that another way is to send the command ":!" to vim. Then, you will view back the terminal, and would be able to see previous commands, until you type "enter" or a new VIM command. Then vim would come back.
Enjoy !
Gilles.
Or just run:shell
, which is more readable. Are those equivalent?
– Wildcard
Feb 15 '16 at 7:35
add a comment |
I think that another way is to send the command ":!" to vim. Then, you will view back the terminal, and would be able to see previous commands, until you type "enter" or a new VIM command. Then vim would come back.
Enjoy !
Gilles.
I think that another way is to send the command ":!" to vim. Then, you will view back the terminal, and would be able to see previous commands, until you type "enter" or a new VIM command. Then vim would come back.
Enjoy !
Gilles.
answered Nov 11 '15 at 17:48
GillesGilles
1
1
Or just run:shell
, which is more readable. Are those equivalent?
– Wildcard
Feb 15 '16 at 7:35
add a comment |
Or just run:shell
, which is more readable. Are those equivalent?
– Wildcard
Feb 15 '16 at 7:35
Or just run
:shell
, which is more readable. Are those equivalent?– Wildcard
Feb 15 '16 at 7:35
Or just run
:shell
, which is more readable. Are those equivalent?– Wildcard
Feb 15 '16 at 7:35
add a comment |
Thanks for contributing an answer to Unix & Linux 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%2funix.stackexchange.com%2fquestions%2f214379%2fmobaxterm-how-to-see-previous-commands-terminal-output-while-still-being-in-vi%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
Can someone please add mobaxterm to the list of tags? It seems I need 300+ points for it.
– Srikanth
Jul 7 '15 at 13:33