[7650] in SIPB bug reports
Re: w3m depends on xterm font choice
daemon@ATHENA.MIT.EDU (John Carr)
Tue Sep 26 10:05:47 2000
Message-Id: <200009261405.KAA16964@nerd-xing.mit.edu>
To: chad <y@MIT.EDU>
cc: bug-sipb@MIT.EDU
In-Reply-To: Your message of "Mon, 25 Sep 2000 12:02:03 EDT."
<200009251603.e8PG33K13256@egon>
Date: Tue, 26 Sep 2000 10:05:38 -0400
From: John Carr <jfc@MIT.EDU>
> We could print a warning about the fonts, but those are typically
> annoying.
> We could modify w3m to optionally clear the screen before scrolling.
That would fix the problem, although it might be better to also avoid
using the invisible line drawing characters. I can already do that
with "env TERM=ansi" so I wouldn't find the command line option
helpful. I don't think an unconditional warning would be a good idea;
I get annoyed that xdvi tells me "overstrike characters may be
incorrect" every time I run it. So unless there is a dotfile fix or
w3m can detect what font is in use, maybe it should be left as-is.
> We could create a wrapper like `xw3m' that started xterm with a
> `compatible' font running w3m (there are even a couple ways to be
> clever with X resources to allow customization).
>
> That's all that comes to mind immediately. Any other suggestions?
> Any preferences from amongst these options?
