Mercurial > emacs
changeset 7429:5c2347e34b31
Allow marker string to arrive in mid-line.
author | Karl Heuer <kwzh@gnu.org> |
---|---|
date | Tue, 10 May 1994 05:58:57 +0000 |
parents | e14086d8ba6f |
children | 1ec8830e553c |
files | lisp/gud.el |
diffstat | 1 files changed, 6 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- a/lisp/gud.el Tue May 10 05:48:20 1994 +0000 +++ b/lisp/gud.el Tue May 10 05:58:57 1994 +0000 @@ -174,7 +174,7 @@ (let ((output "")) ;; Process all the complete markers in this chunk. - (while (string-match "^\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n" + (while (string-match "\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n" gud-marker-acc) (setq @@ -198,7 +198,7 @@ ;; gud-marker-acc until we receive the rest of it. Since we ;; know the full marker regexp above failed, it's pretty simple to ;; test for marker starts. - (if (string-match "^\032.*\\'" gud-marker-acc) + (if (string-match "\032.*\\'" gud-marker-acc) (progn ;; Everything before the potential marker start can be output. (setq output (concat output (substring gud-marker-acc @@ -474,7 +474,7 @@ (while (string-match ;; This is like th gdb marker but with an optional ;; leading break point number like `[1] ' - "^[][ 0-9]*\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n" + "[][ 0-9]*\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n" gud-marker-acc) (setq @@ -498,7 +498,7 @@ ;; gud-marker-acc until we receive the rest of it. Since we ;; know the full marker regexp above failed, it's pretty simple to ;; test for marker starts. - (if (string-match "^[][ 0-9]*\032.*\\'" gud-marker-acc) + (if (string-match "[][ 0-9]*\032.*\\'" gud-marker-acc) (progn ;; Everything before the potential marker start can be output. (setq output (concat output (substring gud-marker-acc @@ -779,7 +779,7 @@ (let ((output "")) ;; Process all the complete markers in this chunk. - (while (string-match "^\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n" + (while (string-match "\032\032\\([^:\n]*\\):\\([0-9]*\\):.*\n" gud-marker-acc) (setq @@ -803,7 +803,7 @@ ;; gud-marker-acc until we receive the rest of it. Since we ;; know the full marker regexp above failed, it's pretty simple to ;; test for marker starts. - (if (string-match "^\032.*\\'" gud-marker-acc) + (if (string-match "\032.*\\'" gud-marker-acc) (progn ;; Everything before the potential marker start can be output. (setq output (concat output (substring gud-marker-acc