On 7 Jun 2008 John-Mark Bell wrote:
> On Fri, 6 Jun 2008, John-Mark Bell wrote:
>> On Fri, 6 Jun 2008, Richard Porter wrote:
>>
>>> Ello, Ello, we've regressed. When I've opened a local file in recent
>>> versions of NetSurf, instead of getting the file I've clicked on I'm
>>> getting an old vers
On Fri, 6 Jun 2008, John-Mark Bell wrote:
On Fri, 6 Jun 2008, Richard Porter wrote:
Ello, Ello, we've regressed. When I've opened a local file in recent
versions of NetSurf, instead of getting the file I've clicked on I'm
getting an old version of the file that's been cached. I thought we'd
go
On Sat, 7 Jun 2008, Keith Hopper wrote:
In article <[EMAIL PROTECTED]>,
John-Mark Bell <[EMAIL PROTECTED]> wrote:
On Fri, 6 Jun 2008, Richard Porter wrote:
There is no point in cacheing local files.
Actually, there is -- it removes the overhead of reprocessing the file
content into what
In article <[EMAIL PROTECTED]>,
John-Mark Bell <[EMAIL PROTECTED]> wrote:
> On Fri, 6 Jun 2008, Richard Porter wrote:
[snip]
> > There is no point in cacheing local files.
> Actually, there is -- it removes the overhead of reprocessing the file
> content into whatever internal representation
On Fri, 6 Jun 2008, Richard Porter wrote:
Ello, Ello, we've regressed. When I've opened a local file in recent
versions of NetSurf, instead of getting the file I've clicked on I'm
getting an old version of the file that's been cached. I thought we'd
got rid of this behaviour a long time ago, but
