Skip to content
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

Value substitution for preprocessor variables (LESS, SASS, Stylus) #33

Open
Isk1n opened this issue Nov 9, 2015 · 3 comments
Open

Value substitution for preprocessor variables (LESS, SASS, Stylus) #33

Isk1n opened this issue Nov 9, 2015 · 3 comments

Comments

@Isk1n
Copy link
Contributor

Isk1n commented Nov 9, 2015

There is a plugin for ST https://github.com/MaciekBaron/sublime-list-stylesheet-vars, which creates a list of currently available variables (both declared and imported!) with corresponding values.

It would be awesome, if you blend your plugins.

@ctf0
Copy link

ctf0 commented Sep 25, 2016

what exactly are u after ? can u show an example ?

@Isk1n
Copy link
Contributor Author

Isk1n commented Sep 26, 2016

Currently your plugin loads predefined lists of completions. It doesn't see my own variables and their values (unless I hardcode them into sbc-api-*.sublime-settings, which isn't practical)

The plugin I mentioned before creates a list of all available variables and their values on the fly. It finds all imports and all declared variables with their values in the current opened document. Then it reads all import files and adds their variables to the list. Unfortunately that plugin doesn't use the list for autocompletion.

Current suggestions:

sbc

What I would like to see:

slsv

I realize that such feature might be out of scope of your plugin, it could greatly impact the performance and it would probably be hard to extend on other languages.

@ctf0
Copy link

ctf0 commented Sep 26, 2016

thats because u mixed up what this plugin is for vs autocompletion or fuzzy search.

this package is mainly a different way or using snippets, so instead of a snippet file per each u simply combine them all in one file under the same scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants