🚀 go-pugleaf

Emacs kindly points out when I've typed mismatched or unmatched
parentheses.  It does this by printing a little message in the echo
area.  But since I'm not too perceptive, I usually don't notice the
little message, so I juggled the function `blink-matching-open' to
ring the bell as well:
	*** simple.el	Fri Mar 30 09:53:50 1990
	--- simple.el~	Fri Mar 30 09:53:25 1990
	***************
	*** 1277,1287 ****
						(end-of-line)
						(point)))))))
		     (cond (mismatch
	! 		    (message "Mismatched parentheses")
	! 		    (ding))
			   ((not blink-matching-paren-distance)
	! 		    (message "Unmatched parenthesis")
	! 		    (ding))))))))

	  ;Turned off because it makes dbx bomb out.
	  (setq blink-paren-hook 'blink-matching-open)
	--- 1277,1285 ----
						(end-of-line)
						(point)))))))
		     (cond (mismatch
	! 		    (message "Mismatched parentheses"))
			   ((not blink-matching-paren-distance)
	! 		    (message "Unmatched parenthesis"))))))))

	  ;Turned off because it makes dbx bomb out.
	  (setq blink-paren-hook 'blink-matching-open)

This is the same as in the 18.55 distribution of `compile.el', except
I've added a `(widen)' right after the offending file is visited.  I
tend to narrow the buffers with my source in them.

	*** /usr/local/emacs18.55/lisp/compile.el	Thu Dec 29 11:25:03 1988
	--- compile.el	Fri Mar 30 09:58:09 1990
	***************
	*** 279,284 ****
	--- 279,285 ----
		      ;; Go to that buffer and find the erring line.
		      (save-excursion
			(set-buffer text-buffer)
	+ 		(widen)
			(if (zerop last-linenum)
			    (progn
			      (goto-char 1)
       ------------------------------------------------------------------------
       |Eric Hanchrow		yamada-sun!eric@nosun.west.sun.com	      |
       |Phase III Logic, Inc.	...!{tektronix, sun}!nosun!yamada-sun!eric    |
       |1600 N.W. 167th Place		Beaverton, OR 97006		      |
       |Voice: (503)-645-0313		Fax: (503)-645-0207    as of 13-Dec-89|
       ------------------------------------------------------------------------