Aristotle Pagaltzis

Glad you enjoy it 🙂 And I deeply appreciate getting this particular praise – not making users jump through hoops for mere convenience on my part without real benefit *to...

Note to self: https://doc.qt.io/qt-5/qml-color.html

Those are the only options I can think of as well. And both of them bug me, though I haven’t fully reasoned out my gut feel. When I tried to...

You got me excited for a minute there until I realised that that cannot work… and then made me realise that actually the whole approach of checking the flag in...

So given that realisation I’m wondering about supporting a plugin load suppression flag at all. I already intend to add a feature to allow users to prevent the plugin from...

So… It’s true that if `g:loaded_css_color_foo` is only *checked* in the corresponding `after/syntax/foo.vim` but never *set* by any code in the plugin, then that part would work. The overall scheme...

No worries. 🙂

So: it’s not going to be a `loaded` flag. Then that means there’s no imperative to try and keep the plugin from loading which means there’s no reason to copy-paste...

If it works, yes. It’s a question of timing, I don’t know off the top of my head whether `after` scripts run after the `FileType` autocommand has been triggered. If...

@BubbatheVTOG: The short answer is, look at `:set filetype?` in the file where you want to enable vim-css-color, and if for example it says `foo`, then make a file `~/.vim/after/syntax/foo.vim`...