shmargum / vim-sass-colors Goto Github PK

After installing with minpac on vim8, nothing happens when opening scss files. I thought it might be something with my folder structure, so I tested the file that has all the definitions it and those wouldn't highlight either.

If I run :echo has('ruby') I get 1 and when running vim --version | grep 'ruby' I get +ruby as part of the output. That should mean my vim has ruby support, correct?

Running :set filetype? on any of the files I've tested outputs filetype=scss, so I don't think there's anything wrong with miss-identification.

I have truecolors enabled in Vim and I am using a truecolor compatible terminal.

I've verified that the plugin's directory is in my run time path and I have filetype plugin indent on in my .vimrc file. I'm pretty new to Vim, so that's about all I've got for trying to figure this out.

• Vim version: VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Oct 17 2017 11:21:47) Included Patches: 1-1300

• Ruby version: ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin16]

• OS version: MacOS 10.13.1 (17B48)

Is there a special case for #eeeeee as it's not colored?

I've noticed that it does the same for rgb(238, 238, 238).

Sass is deprecating @import, so will there be a support for @use?

https://sass-lang.com/documentation/at-rules/import

In my case, this plugin obviously slows down the performance speed of vim. I don't know Vim well, but it seems to slow it down when it goes into buffer. It delays by about a second, when I move the window in <C-w>hjkl or when I use :b to move the When switching buffers. A similar plugin, colorizer, doesn't have this kind of delay. Is it just me? (I'm new to Vim so I don't know how to research it in detail. )

• macos 10.15.5
• vim 8.2.1100 using homebrew
• alacritty 0.4.3

can we support variables below?

:root {
  --gulf-blue: 55, 64, 87;
}

rgb(var(--gulf-blue));
rgba(var(--gulf-blue), 0.5);

For styled-components

https://www.styled-components.com

the plugin works but when I go to the window below the css file I get these errors

Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   11:
E688: More targets than List items
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   12:
E121: Undefined variable: l:guibg
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   14:
E121: Undefined variable: l:group
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   14:
E116: Invalid arguments for function hlexists(l:group) == 0
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   23:
E121: Undefined variable: l:tdx
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   28:
E121: Undefined variable: l:cssname
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   33:
E121: Undefined variable: l:hsl
Press ENTER or type command to continue

I like to use includePaths on my gulp-sass configs to avoid 2 major things:

• Manually copying the sass of a project that is already in my node_modules

• Having to do: ../../../.. infinite 😛

So adding that param you add the path to where you'd like to be able to import things like magic (kind of like with the sass-loader of web pack that you can do @import "~bootstrap/bootstrap.scss";

So my guess is the plugin can't seem to follow those magic imports and in a lot of projects I'm getting these kind of logs

If there's any way I could help I'll be glad to contribute, this plugin is something really cool that brings the best of pigments to vim ❤️