Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy
On Fri, Apr 07, 2017 at 07:23:39AM -0400, G. Branden Robinson wrote:
> At 2017-04-06T21:56:13-0400, James McCoy wrote:
> > On Fri, Apr 07, 2017 at 12:54:19AM +0200, Francesco Poli wrote:
> > > On Thu, 6 Apr 2017 15:06:17 -0400 G. Branden Robinson wrote:
> > >
> > > > At 2017-04-06T13:33:58-0400, James McCoy wrote:
> > > > > On Thu, Apr 06, 2017 at 01:17:55PM -0400, G. Branden Robinson wrote:
> > > > > > The below is not a sufficient reproduction receipe for me.
> > > > > >
> > > > > > I'm running Debian Stretch (testing).
> > > > > >
> > > > > > Things do not go wrong at step #5, nor afterward.
> > > > >
> > > > > Make sure the terminal is sized small enough (80x24). That causes the
> > > > > syntax highlighting in Vim to get a little confused and enable some bold
> > > > > highlighting, which then causes the visual bell to turn everything bold.
> > > >
> > > > It was.
> > >
> > > Hello Branden!
> > > Thanks for trying to reproduce the bug.
> > >
> > > Does it help to know that I have:
> > >
> > > xset b off
> > >
> > > in my ~/.xsession script?
> >
> > I don't think that's relevant. My bell is on. I was also able to
> > reproduce it without causing the bell.
> >
> > I've attached an asciinema recording of me reproducing the problem.
> > When I replay the recording, it causes the same problem to the xterm in
> > which it is running, so hopefully this helps debug the problem.
>
> That's really interesing. I _still_ can't repro this, even playing back
> James's demo with asciinema--a tool of which I wasn't aware, thanks!
>
> I'm launching xterm in GNOME with the GNOME command runner, whatever
> that's called--the Alt+F2 thing.
>
> However, my xterms are somewhat customized. I'm attaching my
> .Xresources file.
Perfect! That seems to be the difference. I, and presumably Francesco, aren't
using TTF fonts. If I change your Xresources to use
XTerm.*.VT100.Font: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
instead of the FaceName/FaceSize resources, then playing the recording
reproduces the problem.
Cheers,
James
Reply to: