Aristotle Pagaltzis

Glad you enjoy it 😊 Netrw is problematic because each directory browser uses *two* buffers – the listed one you navigate to, which is empty, and then another unlisted buffer,...

Bizarre. Doubtful that Pathogen is, err, the pathogen. Maybe you can try co-enabling just one of your other plugins at a time, and see if you can pin down the...

Oh well. Sorry I couldn’t help, and too bad the problem persists (whatever it was that caused it). So it goes. :smile:

> I have a feeling vim-css-color is re-loading the buffer It shouldn’t, and as far as I know it doesn’t. A buffer reload does sound like one plausible explanation for...

(Hmm. Does your `.vimrc` include `syntax on`, even though you’ve not shown it here? If not, how is that getting turned on?)

Something weird is going on here. If I leave the `after/syntax/php.vim` file in place but remove the other `after/syntax/` files (e.g. `css.vim`) (which are all getting loaded indirectly because the...

What’s confusing me is how `vim-css-color` would even be getting loaded if `syntax` is not enabled! 😛 Also, what purpose `let g:php_folding=1` serves, if you have nothing in your `vimrc`...

Well then, one mystery down. Progress!

Support for each filetype has to be implemented separately; see the contents of the `after/syntax/` directory. This is by design. Once added there is no option to disable support for...

(It’s not as straightforward how to make disabling filetypes configurable as it might seem, because of how the plugin is structured with the loaders in `after/syntax/` and the main code...