Timeline for neovim syntax highlight with large files issue
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16, 2021 at 17:34 | history | edited | D. Ben Knoble♦ | CC BY-SA 4.0 |
added 83 characters in body
|
| May 27, 2020 at 12:18 | comment | added | D. Ben Knoble♦ | @Nurjan completely different; Idk what vscode does, but vim’s syntax highlighter is based on regex and a few other things. It’s slow and unwieldy in the long run (though text properties present a new avenue to explore things like tree sitters). | |
| May 27, 2020 at 6:46 | comment | added | Nurjan | I opened the same large xml file in vs code without any problems and the syntax highlighting worked fine. I think there is some specific issue with neovim/vim and it really frustrates me. | |
| May 26, 2020 at 20:44 | comment | added | D. Ben Knoble♦ | @filbranden i’ve has this issue in clojure before where it seemed that having a lot of forms, even if most of them are shallowly nested (which is rare, granted), causes problems. As i said, I dont have anything to back this up, and I’d love to be wrong => maybe there’s an easy fix | |
| May 26, 2020 at 20:03 | comment | added | filbranden |
Looking at $VIMRUNTIME/syntax/xml.vim, I'm not so sure it's that expensive, it doesn't look like it's trying to match tags but only highlight tags, attributes, namespaces, etc. shouldn't be that expensive. There's a comment there about g:xml_syntax_folding making things slower, but that's about it...
|
|
| May 26, 2020 at 13:37 | history | answered | D. Ben Knoble♦ | CC BY-SA 4.0 |