From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-switch Date: Mon, 23 May 2016 20:00:51 +0300 Message-ID: <83bn3w675o.fsf@gnu.org> References: <83oa7x5wpc.fsf@gnu.org> <83k2ik68h2.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1464023085 31494 80.91.229.3 (23 May 2016 17:04:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 May 2016 17:04:45 +0000 (UTC) Cc: rgm@gnu.org, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 23 19:04:38 2016 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 1b4tHS-00010h-HL for ged-emacs-devel@m.gmane.org; Mon, 23 May 2016 19:04:38 +0200 Original-Received: from localhost ([::1]:49423 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b4tHR-0002AI-Nl for ged-emacs-devel@m.gmane.org; Mon, 23 May 2016 13:04:37 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38727) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b4tDy-00005x-N2 for emacs-devel@gnu.org; Mon, 23 May 2016 13:01:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b4tDu-0000kY-QV for emacs-devel@gnu.org; Mon, 23 May 2016 13:01:02 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:45583) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b4tDu-0000k9-O7; Mon, 23 May 2016 13:00:58 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3415 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1b4tDs-0004mq-Fw; Mon, 23 May 2016 13:00:56 -0400 In-reply-to: (message from Paul Eggert on Mon, 23 May 2016 09:44:44 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:203964 Archived-At: > Cc: emacs-devel@gnu.org > From: Paul Eggert > Date: Mon, 23 May 2016 09:44:44 -0700 > > On 05/23/2016 09:32 AM, Eli Zaretskii wrote: > >> >Closed bugs are not included in the list at the top of > >> >http://debbugs.gnu.org/19759 > > They are for me. > > What I've noticed, is that http://debbugs.gnu.org/19759 is often cached > (whether in my browser or somewhere else, I haven't checked), and when I > close a blocking bug the closed bug is still listed on that web page as > a blocker, until I refresh the cache. This is independent of whether the > bug is still listed as a blocker. IME, the bug is still listed as blocking long after it was closed, no matter how many times I refresh the browser page. But when I send the control message to the tracker that unblocks it, the next refresh of the browser updates the display by removing that bug. So if some cache is involved in this, it reacts differently to closing a bug and to removing it from the blockers list. > Glenn is right: it shouldn't be necessary to remove the bug as a > blocking bug. If there is something other than caching that is causing > this problem it'd be nice to know what it is. Hey, I tried, okay? I didn't do it because I deliberately ignored Glenn's requests. I even told him in the past (off list) that what he asks for didn't work for me. I just don't want to let software problems prevent me from doing my job. If there's a bug there somewhere that causes the phenomenon I described above, I'm all for fixing it, and will be the first to avoid sending control messages when it is fixed -- it's not like I enjoy writing those messages. TIA