Re: Bug in rendering <pre>

Tomas Volf <[email protected]> Sun, 16 Mar 2025 22:23:19 +0100
Newsgroups gmane.comp.web.lynx.devel
Message-ID <[email protected]>
Ben Collver <[email protected]> writes:

> On Sun, Mar 16, 2025 at 03:21:07PM +0100, Tomas Volf wrote:
>> Hello,
>> 
>> I hope this is the right place to report bugs.  I think I might have
>> found one in how <pre><code> is rendered.  On my home page[0] I have the
>> following block of code:
>> 
>> In regular browser, it is rendered as this:
>> 
>> However in lynx it ends up looking like the following:
>> 
>> I have tested this with lynx 2.9.2.
>> 
>> Have a nice day,
>> Tomas Volf
>> 
>> 0: https://wolfsden.cz/
>
> This renders correctly for me using 2.9.0dev10 with TERM=tmux-256color.
>
> What is the value of your TERM environment variable?

Oh... This is probably the first case I encountered where `xterm' is not
good enough.  If I set TERM to `rxvt-unicode-256color', it starts
working correctly.  Did not occur to me to verify this, sorry for the
noise.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.