Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ctrl S suspends output in Konsole and other terminal emulators. #8

Closed
ghost opened this issue Sep 13, 2011 · 4 comments
Closed

Ctrl S suspends output in Konsole and other terminal emulators. #8

ghost opened this issue Sep 13, 2011 · 4 comments

Comments

@ghost
Copy link

ghost commented Sep 13, 2011

Hi

First, thanks for the awesome job!. I ran in an issue, tho. I prefer using vim (as opposed to gvim) in konsole. The default mapping is grabbed by konsole and therefore not usable in vim.

I changed the mapping by default to s.

@vladimiroff
Copy link

Actually this is a bit of a problem in gnome-terminal. Because in Konsole you can disable this feature, by going to
Settings -> Configure Profile -> Choose current profile -> Edit Profile -> Advanced Tab
and disable Enable flow control using Ctrl+S and Ctrl+Q

But I also think that Ctrl+S is a bad choice for default keystroke, since the fact that most of the people(this part that does not use gnome-terminal, though :D) map it for :write

@ivanov
Copy link
Owner

ivanov commented Sep 20, 2011

@xowlinx: Did you see @vladimiroff's comment about how to disable the control flow functionality in Konsole?

The problem with just s is that it already has a meaning in command mode, and also that it'd be nice to have the same key combination send lines to ipython regardless of the mode (in visual, in insert, and in command).

@vladimiroff: I'm not seeing a problem in gnome-terminal, and I think it's because I have stty stop undef in my .bashrc - which solves the flow control problems in screen (as well as enables the forward-search for bash). (It appears so, I'll add a not to the readme)

Perhaps in the future - the right thing to do is to no define any bindings, and just provide sample bindings for the user to uncomment. Alternatively, we could define a parameter that tells vim-ipython if it should define binds or not, so folks could do that from their .vimrc

@vladimiroff
Copy link

@ivanov, I didn't know about this option(And since my issue was solved by konsole, I haven't search for it).

Perhaps in the future - the right thing to do is to no define any bindings, and just provide sample bindings for the user to uncomment. - This is a nice solution.

@ivanov
Copy link
Owner

ivanov commented Sep 28, 2011

Ok, I think this issue has been sufficiently documented in the README, and with the new ability to disable default mappings with let g:ipy_perform_mappings=0 in one's .vimrc, I'm going to close this.

@ivanov ivanov closed this as completed Sep 28, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants