Re: *Group* buffer disaster fix

[Hrvoje Niksic <hniksic@srce.hr>]

Lloyd Zusman <ljz@asfast.com> writes:

> > --- mailcap.el.orig	Wed Oct 21 16:27:16 1998
> > +++ mailcap.el	Wed Oct 21 16:27:30 1998
> > @@ -272,11 +272,12 @@
> >  
> >  (defun mailcap-save-binary-file ()
> >    (goto-char (point-min))
> > -  (let ((file (read-file-name
> > -	       "Filename to save as: "
> > -	       (or mailcap-download-directory "~/")))
> > -	(require-final-newline nil))
> > -    (write-region (point-min) (point-max) file)
> > +  (unwind-protect
> > +      (let ((file (read-file-name
> > +		   "Filename to save as: "
> > +		   (or mailcap-download-directory "~/")))
> > +	    (require-final-newline nil))
> > +	(write-region (point-min) (point-max) file))
> >      (kill-buffer (current-buffer))))
> >  
> >  (defun mailcap-maybe-eval ()
> 
> Why do we need to do a `kill-buffer' in this routine at all when
> `(mapcar 'mm-destroy-part gnus-article-mime-handles)' is already
> being done within `gnus-summary-exit' and `gnus-group-exit-hook'?

Because we want the "*mm*" buffer to go away as soon as we're done
with it.  Also, the code killing the buffer was already there -- no
`+' before it.  I only added the unwind-protect bit.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Speak softly and carry a +6 two-handed sword.