Timeline for Syntax highlighting randomly turns off
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2019 at 23:32 | comment | added | Thunderbeef |
If you're editing multiple files at the same time, try checking your autocommands. Maybe there's set instead of setlocal somewhere.
|
|
| Nov 28, 2016 at 3:51 | history | edited | Jonah | CC BY-SA 3.0 |
deleted 580 characters in body
|
| Nov 5, 2016 at 3:52 | comment | added | Jonah |
@Rich, it happened again on the vim help file, I tried this and it said: filetype=help Last set from modeline. so my filetype theory seems wrong, or at least incomplete. i then did :syntax enable and the rest of my windows also lost highlighting.
|
|
| Nov 3, 2016 at 15:20 | comment | added | Rich |
The next time it occurs, try :verbose set filetype? This will a). test whether you are correct that the filetype is being reset. b). tell you what is resetting it.
|
|
| Nov 2, 2016 at 16:46 | comment | added | Jonah | @ChristianBrabandt, Thanks. I did it and got some new info in the process. Please see my update. | |
| Nov 2, 2016 at 16:45 | history | edited | Jonah | CC BY-SA 3.0 |
added 573 characters in body
|
| Nov 2, 2016 at 15:36 | comment | added | Christian Brabandt | try disabling vim-coloresque. It is known to be buggy and there exist better alternatives (which you already have installed) | |
| Nov 2, 2016 at 7:14 | comment | added | Jonah | @muru I updated the OP with that info. Nothing stands out as being an obvious culprit, since I've had all of these installed for months (at least) and this problem has only been going on for 3-4 weeks I'd say. | |
| Nov 2, 2016 at 7:13 | history | edited | Jonah | CC BY-SA 3.0 |
added 545 characters in body
|
| Nov 2, 2016 at 6:06 | comment | added | muru |
We can start by looking only at those that do add syntax highlighting (find ~/.vim -type d -name syntax)
|
|
| Nov 2, 2016 at 6:03 | comment | added | Jonah | @muru thanks for your comment. i think it's likely another plugin is involved. the problem is i have about 50, and since the problem appears so sporadically (and can sometimes not appear for days), testing it systematically my turning off plugins and waiting isn't feasible. not to mention the possibility of plugin interaction being the problem. so i'm looking for either 1) a good guess :) or 2) a systematic way to debug it. | |
| Nov 2, 2016 at 5:11 | comment | added | muru | Syntastic doesn't add any syntax highlighting, only checking. Maybe one of your other plugins might be involved. | |
| Nov 2, 2016 at 5:10 | history | edited | muru |
edited tags
|
|
| Nov 1, 2016 at 19:28 | history | asked | Jonah | CC BY-SA 3.0 |