From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/18035 Path: main.gmane.org!not-for-mail From: Lloyd Zusman Newsgroups: gmane.emacs.gnus.general Subject: Re: *Group* buffer disaster fix Date: 21 Oct 1998 23:14:22 -400 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035156630 4049 80.91.224.250 (20 Oct 2002 23:30:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:30:30 +0000 (UTC) Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id XAA16085 for ; Wed, 21 Oct 1998 23:15:29 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id WAB23413; Wed, 21 Oct 1998 22:15:05 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 21 Oct 1998 22:15:03 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id WAA08204 for ; Wed, 21 Oct 1998 22:14:50 -0500 (CDT) Original-Received: from ljz.asfast.net (gnus@ljz.asfast.net [205.230.75.82]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id XAA16029 for ; Wed, 21 Oct 1998 23:14:31 -0400 (EDT) Original-Received: (from gnus@localhost) by ljz.asfast.net (8.8.7/8.8.7) id XAA28984; Wed, 21 Oct 1998 23:14:22 -0400 Original-To: ding@gnus.org X-Face: "!ga1s|?LNLE3MeeeEYs(%LIl9q[xV9!j4#xf4!**BFW_ihlOb;:Slb>)vy>CJM writes: > Lloyd Zusman writes: > > > I was wondering if the `mapcar' that gets invoked later might break > > something, since the reference to the ` *mm*' buffer will be put into > > the mime handle alist for future deletion, even though that buffer > > gets killed here. > > No, the " *mm*" buffer isn't killed by `mailcap-save-binary-file'; > it's the "*mm*" buffer that's killed. I'll have to go back to the code and review the difference in usage between the leading-space and non-leading-space versions of these buffers. > The latter function is also put into the handle for future automatic > destruction, but that doesn't hurt. There is no policy for whether > "external" viewers should kill the buffer it works in after it's done > -- if the viewer deems is handy, it does, and if not, it's cleaned up > automatically later. I therefore assume that it's guaranteed that these buffers will never be accessed again once `(funcall method)' returns and the buffer references are stored in the handle. I'm relieved. So, it looks like Hrvoje Niksic's patches involving `unwind-protect' are indeed the proper ones to apply. I'm curious: will these patches be incorporated into the next pgnus release, or are you thinking of taking a different approach to eliminate this problem? -- Lloyd Zusman ljz@asfast.com