From 2914f5a116b5b3202eb66ba0f4e626e3473395b6 Mon Sep 17 00:00:00 2001 From: Reuben D'Netto Date: Sun, 15 Feb 2015 18:12:08 +1100 Subject: [PATCH] Added configuration option g:vebugger_edit_cmd --- autoload/vebugger/std.vim | 2 +- doc/vebugger.txt | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/autoload/vebugger/std.vim b/autoload/vebugger/std.vim index d227081..f5e171d 100644 --- a/autoload/vebugger/std.vim +++ b/autoload/vebugger/std.vim @@ -169,7 +169,7 @@ function! s:standardThinkHandlers.moveToCurrentLine(readResult,debugger) dict endif let a:debugger.state.std.location=deepcopy(a:readResult.std.location) if !bufexists(a:readResult.std.location.file) - exe 'new '.(a:readResult.std.location.file) + exe get(g:, 'vebugger_view_source_cmd', 'new').' '.(a:readResult.std.location.file) endif call vebugger#std#updateMarksForFile(a:debugger.state,a:readResult.std.location.file) exe 'sign jump 1 file='.fnameescape(fnamemodify(a:readResult.std.location.file,':p')) diff --git a/doc/vebugger.txt b/doc/vebugger.txt index db8088d..01ef741 100644 --- a/doc/vebugger.txt +++ b/doc/vebugger.txt @@ -94,6 +94,13 @@ argument is supplied when running the debugger: *g:vebugger_path_mdbg_32* No default - use it for the 32bit version of Mdbg *g:vebugger_path_mdbg_64* No default - use it for the 64bit version of Mdbg +When stepping into functions in unopened files, they are opened with :new by +default. This can be configured by setting *g:vebugger_view_source_cmd* + +Example: > + let g:vebugger_view_source_cmd='edit' +< + LAUNCHING DEBUGGERS *vebugger-launching* A debugger's implementation is responsible for starting it. The standard is to