add a configuration option vebugger_ignore_patterns

autoload/vebugger.vim

@@ -63,7 +63,27 @@ endfunction
 
 "Handle a single line from the debugger's interactive shell
 function! s:f_debugger.handleLine(pipeName,line) dict
-    call self.addLineToTerminal(a:pipeName,a:line)
+    let l:ignore_patterns = []
+    if exists('b:vebugger_ignore_patterns')
+        let l:ignore_patterns = b:vebugger_ignore_patterns
+    elseif exists('g:vebugger_ignore_patterns')
+        let l:ignore_patterns = g:vebugger_ignore_patterns
+    endif
+
+    if len(l:ignore_patterns)
+        let l:ignore_the_line = 0
+        for pattern in l:ignore_patterns
+            if match(a:line, pattern) >= 0
+                let l:ignore_the_line = 1
+                break
+            endif
+        endfor
+        if !l:ignore_the_line
+            call self.addLineToTerminal(a:pipeName,a:line)
+        endif
+    else
+        call self.addLineToTerminal(a:pipeName,a:line)
+    endif
 
     let l:readResult=deepcopy(self.readResultTemplate,1)
 

doc/vebugger.txt

@@ -128,6 +128,22 @@ Example: >
     let g:vebugger_use_tags=1
 <
 
+If you want to prevent Vebugger from writing messages in a specific pattern
+on a terminal buffer opened by using |:VBGtoggleTerminalBuffer| command, you
+can use a vim regex pattern in the option *g:vebugger_ignore_patterns* or
+*b:vebugger_ignore_patterns*
+
+Example: >
+    let g:vebugger_ignore_patterns = [
+      \ '^*stopped',
+      \ '^[*^]running',
+      \ 'next$',
+      \ '^&\?display',
+      \ '^&\?continue',
+      \ '\^done$',
+      \ ]
+<
+
 LAUNCHING DEBUGGERS                                      *vebugger-launching*
 
 A debugger's implementation is responsible for starting it. The standard is to