Ticket #2936 (new defect)

Opened 5 years ago

Last modified 3 years ago

Ctrl-O conflict with Vim started from command line

Reported by: powerman Owned by:
Priority: major Milestone: Future Releases
Component: mc-core Version: 4.8.1
Keywords: Cc: gotar@…, mooffie@…
Blocked By: Blocking:
Branch state: no branch Votes for changeset:

Description

Run MC, press F4 to start Vim to edit any file, press Ctrl-O. Everything works as expected - Ctrl-O is handled by Vim and MC didn't try to switch panels.

But if you start vim within mc by typing "vi" or "vi file" in command line under MC panels, then MC will try to handle Ctrl-O pressed in Vim and result in showing panels on first press and showing blank screen on second press.

Change History

comment:1 Changed 5 years ago by andrew_b

What you expect in case of vim running from command line?

comment:2 Changed 5 years ago by powerman

I expect same behavior - Ctrl-O should be handled by Vim, not MC.

If it's impossible to detect running vim (or any other full screen curses app, which is also most likely will not be happy if some background app like mc will intercept it hotkeys), then it would be nice to have *any* way to notify mc to stop handling hotkeys while running some command. This let users to setup aliases/wrapper scripts for commands like vi/vim which will notify mc to stop/start handling hotkeys before/after running requested command.

comment:3 Changed 5 years ago by gotar

  • Cc gotar@… added

Note: after second press ctrl-l usually refreshes background app screen.

comment:4 Changed 4 years ago by sknaumov

I have exactly the opposite problem - I want to be able to use Ctrl-o to get from vim to the shell as I used to do with mcedit, but when vim is invoked by pressing F4, Ctrl-o does not work, even if it is unmapped in vim. May be it has to be an option?

comment:5 Changed 3 years ago by mooffie

  • Cc mooffie@… added
Note: See TracTickets for help on using tickets.