Lines Matching +defs:pending +defs:delete
436 (define-key gud-speedbar-key-map "D" 'gdb-var-delete)
455 ["Delete expression" gdb-var-delete
710 (defvar gud-filter-pending-text nil
770 (setq gud-filter-pending-text nil)
2179 ;; marker, delete gud-marker-acc up to and including the match
2373 ;; from the subprocess before we delete the prompt. If the command
2375 ;; likely be in the first chunk of output received, so we will delete
2380 ;; So - when we want to delete the prompt upon receipt of the next
2381 ;; chunk of debugger output, we position gud-delete-prompt-marker at
2383 ;; delete all text between it and the process output marker. If
2384 ;; gud-delete-prompt-marker points nowhere, we leave the current
2386 (defvar gud-delete-prompt-marker nil)
2454 (set (make-local-variable 'gud-delete-prompt-marker) (make-marker))
2559 (setq gud-filter-pending-text
2560 (concat (or gud-filter-pending-text "") string))
2567 (if gud-filter-pending-text
2568 (setq string (concat gud-filter-pending-text string)
2569 gud-filter-pending-text nil))
2572 ;; If we have been so requested, delete the debugger prompt.
2575 (if (marker-buffer gud-delete-prompt-marker)
2577 (delete-region (process-mark proc)
2578 gud-delete-prompt-marker)
2580 (set-marker gud-delete-prompt-marker nil)))
2609 (if gud-filter-pending-text
2654 ;; is dead, we can delete it now. Otherwise it
2656 (delete-process proc))
2831 (if (marker-position gud-delete-prompt-marker)
2833 (goto-char gud-delete-prompt-marker)
2837 (set-marker gud-delete-prompt-marker (point)))
2868 (set-marker gud-delete-prompt-marker (point))
2869 (set-marker-insertion-type gud-delete-prompt-marker t))