Re: eww

[Lars Magne Ingebrigtsen]

Eli Zaretskii <address@hidden> writes:

> Why do you want to limit the number of buffers Emacs keeps?  Other
> browsers don't, I think.

Other buffers don't keep the page around in memory at all, but most of
them have some sort of caching ability -- by writing the HTML/CSS/etc do
disk, and going back in history just fetches the data and re-renders it.

> When you go back to a previously visited URL, do you need to check if
> it's outdated?  Do other browsers?

Other browsers do, and I hate that behaviour.  If I want to see the page
I just saw, why shouldn't I be able to?  Other browsers respect cache
settings and (sensibly) don't write stuff to the disk cache if the
server says it shouldn't.  But Emacs could keep (some) buffers around
and avoid the problem.

There's a potential security issue here, though -- if the server said
"don't cache this page", then it might be because there's secret stuff
that we shouldn't keep around longer than the user expects it to be kept
around.

> I'm confused: don't you name each buffer according to the URL it
> shows?

No, the eww buffer is currently called "*eww*".

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/