Re: Fixed CSS's class name highlight was broken in some cases

2017-01-13 Fir de Conversatie Ryuichi Hayashida
2017年1月14日土曜日 5時53分05秒 UTC+9 Bram Moolenaar: > Ryuichi Hayashida wrote: > > > Hi Jules, Bram, and team > > > > I found that highlight of CSS's class names is broken in below cases: > > > > - class name is one character > > - class name starts with unde

Fixed CSS's class name highlight was broken in some cases

2017-01-13 Fir de Conversatie Ryuichi Hayashida
Hi Jules, Bram, and team I found that highlight of CSS's class names is broken in below cases: - class name is one character - class name starts with under score I fixed them. Please find attached css.vim.patch. Repro: Execute below shell commands - $ cat

Nested substitute() calls break highlights in Vim script

2017-01-08 Fir de Conversatie Ryuichi Hayashida
Hi Bram and all, I found that syntax highlight in Vim script is broken in some situation. When nested substitute() calls are in code, first one is highlighted as vimFuncName and second one is highlighted as vimSubst. How to reproduce this is saving below code as blah.vim and open it in vim with

Re: Patch 7.4.944

2015-11-29 Fir de Conversatie Ryuichi Hayashida
I think assertion message is very important reported when it fails. Should message be customizable as many assertions in other languages? assertEqual({exp}, {act} [, {msg}]) assertFalse({actual} [, {msg}]) assertTrue({actual} [, {msg}]) This is used as below.

Backward reference fails in some cases

2013-10-10 Fir de Conversatie Ryuichi Hayashida
Hello. I would report a bug of regexp. * Problem aba =~# '^\(.\+\).*\1$' This expression is equivalent to 1 when 'regexpengine' is set to 1. However, when it is set to 0 or 2, the expression is equivalent to 0. Backward reference seems to fail. Note that below expression gets 1 whatever