* detecting errors
@ 2006-10-10 10:11 Andreas Roehler
0 siblings, 0 replies; only message in thread
From: Andreas Roehler @ 2006-10-10 10:11 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-10-10 10:11 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-10 10:11 detecting errors Andreas Roehler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).