Dominique Pellé

To bug reporter @Shane-XB-Qian : can you try to reproduce with a asan build? * it should make the bug more reproducible * and if the bug happens, it will...

I am not able to reproduce, but I'm not using KDE (I'm using xubuntu-14.04) and KDE seems to be needed to reproduce this somehow. Could you try to reproduce when:...

@jeking3 wrote: > Sounds like a fair amount of work. Indeed. At least, before we retire the libs/date_time/data/date_time_zonespec.csv builtin file, can we at least provide script or instructions on how...

@jeking3 wrote: > We REALLY need to be able to parse AND fully understand the IANA database to be correct. Understood. I found https://github.com/HowardHinnant/date after posting my previous comment. Howard's...

* the 1st character is U+2202 i.e. UTF8 sequence 0xe2 0x88 0x82 * the 2nd character is a composing character U+2202 + U+0305 i.e. UTF8 sequence 0xe2 0x88 0x82 +...

Maybe it's related with the TODO comment at line `regexp_nfa.c:160`: ``` 3678 case NFA_COMPOSING: // char with composing char 3679 #if 0 !!3680 // TODO 3681 if (regflags & RF_ICOMBINE)...

I could reproduce the crash with vim-8.2.2353. But it no longer happen after vim-8.2.2354. To @yifengchen-cc : can you confirm that the issue can be closed?

@yifengchen-cc wrote: > However，this poc will cause vim to hang I suspect that it's because autocommand like "au * * …" triggers on every events, and the autocomand may trigger...

To @jidhub : could you try to try to reproduce with a asan build of Vim? Maybe your `~/.vimrc` & plugins make this reproducible. You can build with asan by...

@mattn wrote: > For example, Vim also can fix this easily. 1) Your suggested fix still has side effects. If user has set VIMRUNTIME before running vim, then I would...