diff options
| author | Lucas Hoffmann <l-m-h@web.de> | 2017-07-01 11:42:55 +0200 |
|---|---|---|
| committer | Lucas Hoffmann <l-m-h@web.de> | 2018-08-08 23:50:15 +0200 |
| commit | a611781e422d291015e8befcf3afd51dd0aba0fa (patch) | |
| tree | e16cb706ec40f075c3c02474906e381357ed1863 /plugin/vdebug.vim | |
| parent | 7b26de5dfa8d2f9edd50335a8bb3b8bf2f0d58a6 (diff) | |
| download | vdebug-a611781e422d291015e8befcf3afd51dd0aba0fa.zip | |
Remove doautocmd on VdebugPre and VdebugPost
These autocmds could be defined by the user and would have been run at
the beginning and end of plugin/vdebug.vim. They are removed as they
where never documented. Also there exist other options in vim to
achieve the same: Code that should be executed before loading the plugin
file can go into the vimrc file and code that should be executed after
the plugin was loaded can go into the after directory. These are
standard vim mechanisms and they are properly documented (see `:help
after-directory` and `:help vimrc`).
Diffstat (limited to 'plugin/vdebug.vim')
| -rw-r--r-- | plugin/vdebug.vim | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/plugin/vdebug.vim b/plugin/vdebug.vim index 1a7774f..6af9a4e 100644 --- a/plugin/vdebug.vim +++ b/plugin/vdebug.vim @@ -34,8 +34,6 @@ if !has("python3") finish endif -silent doautocmd User VdebugPre - " Nice characters get screwed up on windows if has('win32') || has('win64') let g:vdebug_force_ascii = 1 @@ -301,7 +299,6 @@ function! Vdebug_statusline() return pyeval("debugger.status_for_statusline()") endfunction -silent doautocmd User VdebugPost augroup Vdebug autocmd VimLeavePre * python3 debugger.close() augroup END |