From: Eli Zaretskii <eliz@gnu.org>
To: Chad Brown <yandros@gmail.com>
Cc: emacs-devel@gnu.org
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 [thread overview]
Message-ID: <837fei4zy8.fsf@gnu.org> (raw)
In-Reply-To: <F16FEEC7-CD5C-491D-B0C6-B63562AF0BCF@gmail.com> (message from Chad Brown on Tue, 24 May 2016 18:22:33 -0700)
> From: Chad Brown <yandros@gmail.com>
> Date: Tue, 24 May 2016 18:22:33 -0700
> Cc: emacs-devel <emacs-devel@gnu.org>
>
> 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.
next prev parent reply other threads:[~2016-05-25 2:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83oa7x5wpc.fsf@gnu.org>
[not found] ` <handler.s.C.146397087814700.transcript@debbugs.gnu.org>
2016-05-23 15:40 ` Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-switch Glenn Morris
2016-05-23 16:32 ` Eli Zaretskii
2016-05-23 16:44 ` Paul Eggert
2016-05-23 17:00 ` Eli Zaretskii
2016-05-23 17:32 ` Paul Eggert
2016-05-23 17:41 ` Eli Zaretskii
2016-05-23 18:28 ` John Wiegley
2016-05-23 18:39 ` John Mastro
2016-05-23 18:48 ` Eli Zaretskii
2016-05-24 3:50 ` John Wiegley
2016-05-24 15:38 ` Glenn Morris
2016-05-24 15:41 ` Kaushal Modi
2016-05-24 15:59 ` Eli Zaretskii
2016-05-24 16:47 ` Paul Eggert
2016-05-24 17:25 ` Eli Zaretskii
2016-05-25 1:22 ` Chad Brown
2016-05-25 2:46 ` Eli Zaretskii [this message]
2016-05-25 5:13 ` Paul Eggert
2016-05-26 17:00 ` Glenn Morris
2016-05-26 18:09 ` Glenn Morris
2016-05-25 18:23 ` Paul Eggert
2016-05-25 18:51 ` Clément Pit--Claudel
2016-05-25 18:56 ` Clément Pit--Claudel
2016-05-25 19:33 ` Dmitry Gutov
2016-05-25 21:51 ` Paul Eggert
2016-05-26 2:44 ` Eli Zaretskii
2016-05-26 5:08 ` Paul Eggert
2016-05-26 15:09 ` Eli Zaretskii
2016-05-26 15:27 ` Paul Eggert
2016-05-26 15:48 ` Eli Zaretskii
2016-05-26 16:01 ` Paul Eggert
2016-05-26 16:43 ` John Wiegley
2016-05-26 16:51 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837fei4zy8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yandros@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.