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: Thu, 26 May 2016 05:44:22 +0300 Message-ID: <83oa7t35dl.fsf@gnu.org> References: <83oa7x5wpc.fsf@gnu.org> <83k2ik68h2.fsf@gnu.org> <83bn3w675o.fsf@gnu.org> <834m9o659c.fsf@gnu.org> <83fut74fbu.fsf@gnu.org> <5745F418.1070508@gmail.com> <8107393c-81e6-8422-cebf-f372bc0061bd@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1464230675 26263 80.91.229.3 (26 May 2016 02:44:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 26 May 2016 02:44:35 +0000 (UTC) Cc: clement.pit@gmail.com, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 26 04:44:30 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 1b5lHh-0003hD-PK for ged-emacs-devel@m.gmane.org; Thu, 26 May 2016 04:44:29 +0200 Original-Received: from localhost ([::1]:36139 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5lHg-0005al-Q1 for ged-emacs-devel@m.gmane.org; Wed, 25 May 2016 22:44:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33832) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5lHb-0005af-4w for emacs-devel@gnu.org; Wed, 25 May 2016 22:44:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b5lHV-0007Ip-U2 for emacs-devel@gnu.org; Wed, 25 May 2016 22:44:22 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59413) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5lHV-0007Ia-Qa; Wed, 25 May 2016 22:44:17 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2053 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1b5lHT-00084n-Ue; Wed, 25 May 2016 22:44:16 -0400 In-reply-to: <8107393c-81e6-8422-cebf-f372bc0061bd@cs.ucla.edu> (message from Paul Eggert on Wed, 25 May 2016 14:51:32 -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:204022 Archived-At: > From: Paul Eggert > Date: Wed, 25 May 2016 14:51:32 -0700 > > > Doing a hard refresh forces Firefox to bypass its cache; but ideally, > > debbugs should respond correctly to Firefox' queries and indicate that > > the page was in fact modified. > > Yes, the bug is clearly on the debbugs side here. That being said, the > workaround is to use a shift-reload, which causes Firefox to specify > "cache-control: no"in its request, which in turn causes debbugs to > recalculate the page. The bug seems to be that the removal of a closed bug from the blockers list takes several hours, which is much more than one can be reasonably expect to wait. For example, one bug was closed yesterday 6.5 hours before I got to refreshing the list, and then just clicking the refresh icon showed the updated list. By contrast, explicitly removing a bug from the list by a debbugs command results in an instant update that doesn't need any workarounds. That said, all this thread is a tempest in a teapot, because adding a bug to the list (if it becomes open again) takes just a few moments.