Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy
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.
> At 2017-04-05T22:03:50-0400, James McCoy wrote:
> > On Mon, Mar 20, 2017 at 10:29:20PM +0100, Francesco Poli (wintermute) wrote:
> > > I finally found a reliable way to reproduce it.
> > >
> > > Steps to reproduce:
> > >
> > > 0) open the attached test.md file:
> > >
> > > $ vim -u NONE test.md
> > >
> > > 1) enable syntax highlighting:
> > >
> > > :set bg=dark
> > > :syn on
> > >
> > > 2) go to the end of the file:
> > >
> > > [Shift+G]
> > >
> > > 3) go back to the beginning of the file (line by line):
> > >
> > > [k].....[k] ← hold the key pressed until you reach the first line
> > >
> > > 4) visualize file info on the status line:
> > >
> > > [Ctrl+G]
> > >
> > > 5) the syntax highlighting has gone crazy (even the status line is
> > > in boldface!): see the attached screenshot
> > > wrong_vim_syntaxmarkdown.png
> > >
> > > 6) exit from vim:
> > >
> > > :q
> > >
> > > 7) the terminal (xterm), or rather the shell (bash), has also gone
> > > crazy (it now prints everything in boldface by default): see
> > > the attached screenshot
> > > wrong_vim_syntaxmarkdown2.png
> > >
> > > 8) the terminal won't come back to normal behavior until I quit it;
> > > another trick to regain the normal behavior of the terminal is
> > > opening test.md again, enable syntax highlighting, and exit vim
> > > (steps 0, 1, and 6 above)
>
> Regards,
> Branden
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Reply to: