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: Wed, 25 May 2016 05:46:23 +0300 Message-ID: <837fei4zy8.fsf@gnu.org> References: <83oa7x5wpc.fsf@gnu.org> <83k2ik68h2.fsf@gnu.org> <83bn3w675o.fsf@gnu.org> <834m9o659c.fsf@gnu.org> <83fut74fbu.fsf@gnu.org> <83bn3v4bcj.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1464144425 31713 80.91.229.3 (25 May 2016 02:47:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 25 May 2016 02:47:05 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chad Brown Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 25 04:47:04 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 1b5Oqe-0000bw-Bo for ged-emacs-devel@m.gmane.org; Wed, 25 May 2016 04:47:04 +0200 Original-Received: from localhost ([::1]:56836 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5Oqd-0001a6-Hf for ged-emacs-devel@m.gmane.org; Tue, 24 May 2016 22:47:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35747) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5Oq3-0001Zo-Pv for emacs-devel@gnu.org; Tue, 24 May 2016 22:46:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b5Opx-000192-SB for emacs-devel@gnu.org; Tue, 24 May 2016 22:46:26 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41889) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5Opx-00018v-P6; Tue, 24 May 2016 22:46:21 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1077 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1b5Opv-0003UC-WC; Tue, 24 May 2016 22:46:20 -0400 In-reply-to: (message from Chad Brown on Tue, 24 May 2016 18:22:33 -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:203992 Archived-At: > From: Chad Brown > Date: Tue, 24 May 2016 18:22:33 -0700 > Cc: emacs-devel > > That makes no sense at all. It's the same browser and the same Web > page. How can the browser know to refresh it in one case, but not in > the other? > > Because the refresh button doesn’t ask the web server for a new copy of the page; it instead asks the local > cache to check and see if it thinks a new copy of the web page is needed. There are many circumstances > where the local cache controller can ask the web server and get back what is effectively the wrong answer. So you are saying that this always brings the cached copy when a bug is closed, and always brings the correct copy when a bug is deleted from the blocking list? That makes no sense to me: the browser and the cache don't understand the semantics of each operation at all, so I don't see how they could do different stuff in each case.