On Thu, Mar 06, 2025 at 08:54:16AM +0100, Rene Kita wrote: > On Tue, Mar 04, 2025 at 11:55:02AM +0000, Stuart Henderson wrote: > > On 2025-03-04, Rene Kita <m...@rkta.de> wrote: > > > On Sat, Mar 01, 2025 at 07:34:31AM -0500, Jon Fineman wrote: > > >> I have been having some trouble with emacs/w3m for a while now. > > >> > > >> When I browse lobste.rs I get the below error message. Using the > > >> command line w3m it works fine. duckduckgo.com and a few others also > > >> fail. > > > > > > AFAIK emacs/w3m basically uses 'w3m -dump' to get the rendered page. One > > > difference between interactive usage and using -dump is that w3m won't > > > ask when there is e.g. a certificate or cookie problem. Instead it will > > > fall back to some default. > > > > This is the compression-related problem again. For some reason it's > > now breaking with the reversion of e933cf831f32f but working if > > e933cf831f32f is re-applied. > > Thanks to all the pointers I managed to find the commit which appears to > be the root cause for this. The issues should be fixed in the latest > commit 32193d61 (Fix -dump_source on compressed streams, 2025-03-05).
That fix makes sense to me. Thanks for the quick turnaround. > Below is the patch to update the -current port to the latest head. Committed, thank you!
