Pressing “Ctrl + S” by mistake while using Vim












-2















If you press Ctrl + s while using vim would result with vim to look like as if it is being locked/stuck without you being able to make more changes unless you press Ctrl + q.



Could someone explain what is happening and why?




Hint - it might be something to do with the OS's terminal driver! ;-)




Due to a negative initial perception from the community despite having hinted that this was nothing to do with vim but some novice may search for a solution with regards to vim anyway, I would add:




  • This is a duplicate question to many questions, only seen from a different perspective

  • Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

  • More info about Software flow control here

  • For remote hosts you can disable Ctrl-S (XOFF) START/STOP signals

  • Does Ctrl-S actually stop the process on terminal?


I hope the updated question is much more useful.










share|improve this question




















  • 2





    Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

    – DavidPostill
    Jan 5 at 20:12













  • It's me being funny, I can post an answer myself :-) if people get irritated by the question I will happily delete it. Otherwise we might keep it as it could help people who are yet to experience this as they may search for a solution using different wording. Cheers!

    – dankilev
    Jan 5 at 20:20
















-2















If you press Ctrl + s while using vim would result with vim to look like as if it is being locked/stuck without you being able to make more changes unless you press Ctrl + q.



Could someone explain what is happening and why?




Hint - it might be something to do with the OS's terminal driver! ;-)




Due to a negative initial perception from the community despite having hinted that this was nothing to do with vim but some novice may search for a solution with regards to vim anyway, I would add:




  • This is a duplicate question to many questions, only seen from a different perspective

  • Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

  • More info about Software flow control here

  • For remote hosts you can disable Ctrl-S (XOFF) START/STOP signals

  • Does Ctrl-S actually stop the process on terminal?


I hope the updated question is much more useful.










share|improve this question




















  • 2





    Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

    – DavidPostill
    Jan 5 at 20:12













  • It's me being funny, I can post an answer myself :-) if people get irritated by the question I will happily delete it. Otherwise we might keep it as it could help people who are yet to experience this as they may search for a solution using different wording. Cheers!

    – dankilev
    Jan 5 at 20:20














-2












-2








-2








If you press Ctrl + s while using vim would result with vim to look like as if it is being locked/stuck without you being able to make more changes unless you press Ctrl + q.



Could someone explain what is happening and why?




Hint - it might be something to do with the OS's terminal driver! ;-)




Due to a negative initial perception from the community despite having hinted that this was nothing to do with vim but some novice may search for a solution with regards to vim anyway, I would add:




  • This is a duplicate question to many questions, only seen from a different perspective

  • Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

  • More info about Software flow control here

  • For remote hosts you can disable Ctrl-S (XOFF) START/STOP signals

  • Does Ctrl-S actually stop the process on terminal?


I hope the updated question is much more useful.










share|improve this question
















If you press Ctrl + s while using vim would result with vim to look like as if it is being locked/stuck without you being able to make more changes unless you press Ctrl + q.



Could someone explain what is happening and why?




Hint - it might be something to do with the OS's terminal driver! ;-)




Due to a negative initial perception from the community despite having hinted that this was nothing to do with vim but some novice may search for a solution with regards to vim anyway, I would add:




  • This is a duplicate question to many questions, only seen from a different perspective

  • Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

  • More info about Software flow control here

  • For remote hosts you can disable Ctrl-S (XOFF) START/STOP signals

  • Does Ctrl-S actually stop the process on terminal?


I hope the updated question is much more useful.







keyboard-shortcuts vim






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 7 at 19:21







dankilev

















asked Jan 5 at 20:06









dankilevdankilev

14




14








  • 2





    Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

    – DavidPostill
    Jan 5 at 20:12













  • It's me being funny, I can post an answer myself :-) if people get irritated by the question I will happily delete it. Otherwise we might keep it as it could help people who are yet to experience this as they may search for a solution using different wording. Cheers!

    – dankilev
    Jan 5 at 20:20














  • 2





    Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

    – DavidPostill
    Jan 5 at 20:12













  • It's me being funny, I can post an answer myself :-) if people get irritated by the question I will happily delete it. Otherwise we might keep it as it could help people who are yet to experience this as they may search for a solution using different wording. Cheers!

    – dankilev
    Jan 5 at 20:20








2




2





Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

– DavidPostill
Jan 5 at 20:12







Answered at History of Ctrl-S and Ctrl-Q for flow control and What is the point of Ctrl-S?

– DavidPostill
Jan 5 at 20:12















It's me being funny, I can post an answer myself :-) if people get irritated by the question I will happily delete it. Otherwise we might keep it as it could help people who are yet to experience this as they may search for a solution using different wording. Cheers!

– dankilev
Jan 5 at 20:20





It's me being funny, I can post an answer myself :-) if people get irritated by the question I will happily delete it. Otherwise we might keep it as it could help people who are yet to experience this as they may search for a solution using different wording. Cheers!

– dankilev
Jan 5 at 20:20










1 Answer
1






active

oldest

votes


















1














Well, It's no a vim issue. This is called Software flow control. There is a bunch of info out there on the internet.



According to an article in here:




CTRL-S (XOFF) is part of Software flow control. XOFF notifies the process or device sending data that the input buffer is full and it shouldn't send any more data. The software (outputting process, firmware, terminal etc) can choose how to handle the notification - i.e. keep running and buffer data, drop data, pause until XON is received, etc.




More info about Software flow control here.



NOTE: if you want to get the control of your terminal after you pressed CTRL + s key combination, you can press CTRL + q.



I hope this helps.






share|improve this answer
























  • Note that if it's a annoyance you can disable Ctrl-s on Linux by adding stty stop "" to one of your start-up scripts (eg ~/.bashrc).

    – AFH
    Jan 5 at 20:44











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f1390977%2fpressing-ctrl-s-by-mistake-while-using-vim%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









1














Well, It's no a vim issue. This is called Software flow control. There is a bunch of info out there on the internet.



According to an article in here:




CTRL-S (XOFF) is part of Software flow control. XOFF notifies the process or device sending data that the input buffer is full and it shouldn't send any more data. The software (outputting process, firmware, terminal etc) can choose how to handle the notification - i.e. keep running and buffer data, drop data, pause until XON is received, etc.




More info about Software flow control here.



NOTE: if you want to get the control of your terminal after you pressed CTRL + s key combination, you can press CTRL + q.



I hope this helps.






share|improve this answer
























  • Note that if it's a annoyance you can disable Ctrl-s on Linux by adding stty stop "" to one of your start-up scripts (eg ~/.bashrc).

    – AFH
    Jan 5 at 20:44
















1














Well, It's no a vim issue. This is called Software flow control. There is a bunch of info out there on the internet.



According to an article in here:




CTRL-S (XOFF) is part of Software flow control. XOFF notifies the process or device sending data that the input buffer is full and it shouldn't send any more data. The software (outputting process, firmware, terminal etc) can choose how to handle the notification - i.e. keep running and buffer data, drop data, pause until XON is received, etc.




More info about Software flow control here.



NOTE: if you want to get the control of your terminal after you pressed CTRL + s key combination, you can press CTRL + q.



I hope this helps.






share|improve this answer
























  • Note that if it's a annoyance you can disable Ctrl-s on Linux by adding stty stop "" to one of your start-up scripts (eg ~/.bashrc).

    – AFH
    Jan 5 at 20:44














1












1








1







Well, It's no a vim issue. This is called Software flow control. There is a bunch of info out there on the internet.



According to an article in here:




CTRL-S (XOFF) is part of Software flow control. XOFF notifies the process or device sending data that the input buffer is full and it shouldn't send any more data. The software (outputting process, firmware, terminal etc) can choose how to handle the notification - i.e. keep running and buffer data, drop data, pause until XON is received, etc.




More info about Software flow control here.



NOTE: if you want to get the control of your terminal after you pressed CTRL + s key combination, you can press CTRL + q.



I hope this helps.






share|improve this answer













Well, It's no a vim issue. This is called Software flow control. There is a bunch of info out there on the internet.



According to an article in here:




CTRL-S (XOFF) is part of Software flow control. XOFF notifies the process or device sending data that the input buffer is full and it shouldn't send any more data. The software (outputting process, firmware, terminal etc) can choose how to handle the notification - i.e. keep running and buffer data, drop data, pause until XON is received, etc.




More info about Software flow control here.



NOTE: if you want to get the control of your terminal after you pressed CTRL + s key combination, you can press CTRL + q.



I hope this helps.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 5 at 20:27









Manuel FlorianManuel Florian

1595




1595













  • Note that if it's a annoyance you can disable Ctrl-s on Linux by adding stty stop "" to one of your start-up scripts (eg ~/.bashrc).

    – AFH
    Jan 5 at 20:44



















  • Note that if it's a annoyance you can disable Ctrl-s on Linux by adding stty stop "" to one of your start-up scripts (eg ~/.bashrc).

    – AFH
    Jan 5 at 20:44

















Note that if it's a annoyance you can disable Ctrl-s on Linux by adding stty stop "" to one of your start-up scripts (eg ~/.bashrc).

– AFH
Jan 5 at 20:44





Note that if it's a annoyance you can disable Ctrl-s on Linux by adding stty stop "" to one of your start-up scripts (eg ~/.bashrc).

– AFH
Jan 5 at 20:44


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • 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%2fsuperuser.com%2fquestions%2f1390977%2fpressing-ctrl-s-by-mistake-while-using-vim%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

Plaza Victoria

Puebla de Zaragoza

Musa