From 963c1ad5d072346d9e95d4c3be066b5e03c601d3 Mon Sep 17 00:00:00 2001 From: Bram Moolenaar Date: Thu, 19 Jul 2018 02:55:01 +0200 Subject: patch 8.1.0195: terminal debugger commands don't always work Problem: Terminal debugger commands don't always work. (Dominique Pelle) Solution: Set 'cpo' to its default value when defining commands. (Christian Brabandt) --- runtime/pack/dist/opt/termdebug/plugin/termdebug.vim | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'runtime/pack/dist/opt') diff --git a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim index 4ccbc4cb66..63a3b1d83d 100644 --- a/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim +++ b/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim @@ -566,6 +566,9 @@ endfunc " Install commands in the current window to control the debugger. func s:InstallCommands() + let save_cpo = &cpo + set cpo&vim + command Break call s:SetBreakpoint() command Clear call s:ClearBreakpoint() command Step call s:SendCommand('-exec-step') @@ -603,6 +606,8 @@ func s:InstallCommands() an 1.230 PopUp.Evaluate :Evaluate endif endif + + let &cpo = save_cpo endfunc let s:winbar_winids = [] -- cgit v1.2.3