From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Tromey Newsgroups: gmane.emacs.devel Subject: Re: threads and kill-buffer Date: Wed, 05 Sep 2012 12:20:38 -0600 Message-ID: <87d320qqkp.fsf@fleche.redhat.com> References: <87a9x55xvd.fsf@fleche.redhat.com> <83d321dvsr.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1346869247 10297 80.91.229.3 (5 Sep 2012 18:20:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Sep 2012 18:20:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 05 20:20:49 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1T9KDY-0001Ll-G6 for ged-emacs-devel@m.gmane.org; Wed, 05 Sep 2012 20:20:48 +0200 Original-Received: from localhost ([::1]:49930 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T9KDV-0007HZ-Ha for ged-emacs-devel@m.gmane.org; Wed, 05 Sep 2012 14:20:45 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:51042) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T9KDS-0007HJ-R8 for emacs-devel@gnu.org; Wed, 05 Sep 2012 14:20:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T9KDQ-00074O-S7 for emacs-devel@gnu.org; Wed, 05 Sep 2012 14:20:42 -0400 Original-Received: from mx1.redhat.com ([209.132.183.28]:33034) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T9KDQ-00074G-Jv; Wed, 05 Sep 2012 14:20:40 -0400 Original-Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q85IKduc008168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Sep 2012 14:20:39 -0400 Original-Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q85IKcuv023472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 5 Sep 2012 14:20:39 -0400 X-Attribution: Tom In-Reply-To: <83d321dvsr.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Sep 2012 05:53:56 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.132.183.28 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:153065 Archived-At: >>>>> "Eli" == Eli Zaretskii writes: Eli> How about letting kill-buffer succeed, but delay the actual deletion Eli> of the buffer until no thread has it as current, like what Posix Eli> filesystems do with file deletion? I think that's a very interesting idea, thanks. I have been thinking about it and the only issue I see is that, since it introduces a new buffer state, we would have to decide what buffer-live-p returns for a buffer that is killed-but-not-yet-dead. I suppose we may also want a new predicate to detect this state. Tom