detecting errors

detecting errors

[Andreas Roehler]

While editing a larger file a function definition was
mutilated inadvertently.

I.e. beginning part was killed, remaining code saved as shown
below.

  ;;
  (goto-char (point-min))
  (while (re-search-forward "\\(^\"[ \t]+\\)" nil t)
    (progn (replace-match "\"")
       (message "%s" (what-line))))

    (goto-char (point-min))
    (while (re-search-forward "\\([ \t]+\\)" nil t)
      (progn (replace-match " ")
         (message "%s" (what-line))))

Detecting this error turned out laborious, as `(check
parens)', which often is helpful, couldn't claim
anything wrong. Also byte-compile-file finished without
error-messages.

Is there an appropriate way to locate this kind of errors?

Thanks

__
Andreas Roehler