-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get syntax highlighting to work on nixos #111
Comments
I'm having the same problem. |
Found a solution for NixOS using home-manager. Basically, add plugins using the vim-plug config option: {
programs.neovim = {
enable = true;
viAlias = true;
configure = {
customRC = ''
let $NVIM_TUI_ENABLE_TRUE_COLOR=1
let g:haskell_enable_quantification = 1 " to enable highlighting of `forall`
let g:haskell_enable_recursivedo = 1 " to enable highlighting of `mdo` and `rec`
let g:haskell_enable_arrowsyntax = 1 " to enable highlighting of `proc`
let g:haskell_enable_pattern_synonyms = 1 " to enable highlighting of `pattern`
let g:haskell_enable_typeroles = 1 " to enable highlighting of type roles
let g:haskell_enable_static_pointers = 1 " to enable highlighting of `static`
let g:haskell_backpack = 1 " to enable highlighting of backpack keywords
'';
plug.plugins = with pkgs.vimPlugins; [
haskell-vim
];
};
};
} |
My config above doesn't work anymore, not sure why. I haven't noticed for a while but I'm assuming it happened around either the NixOS 19.09 or 20.03 upgrade. |
@emptyflask I can confirm that it stopped working for me somewhat around the same time. :-( |
Apparently this is caused by a wrong load order of plugins. This plugin has to be before the nvim-runtime in the runtime-path. The first syntax file wins. @emptyflask It is fixed on nixos-unstable and I made a PR to fix it on stable. NixOS/nixpkgs#87543 |
Using the following nix overlay, I can't get this plugin to work:
Steps to reproduce:
Expected: good syntax highlighting.
Actual: default syntax highlighting.
If somebody else using nix can get this working it would be good to know!
The text was updated successfully, but these errors were encountered: