Isaac Muse

Here's the thing. I have the capability to parse, that part isn't hard. But this requires us to parse the whole file every time to get the context of all...

@rwols I believe had made a suggestion while I was kneedeep in re-writing ColorHelper about somehow connecting LSP with ColorHelper. At the time I was so overwhelmed with work that...

> Can you make it work for built-in variables like `--background` and `--accent` etc. ? The problems for built-in variables and other custom variables remain the same. Nothing is made...

Can you elaborate? I'm not sure what your mean.

Are you proposing it always loads the variables from the currently loaded color-scheme? Looks at the current active buffer and loads variables from there? Some combination? While I'm not sure...

I don't think `var(view.--name)` is a thing.

One of the reasons I'm not too keen on including variables is because it isn't even as simple as just get the current variables. There are complexities when trying to...

> I don't think considering overloads is necessary, just go the easy way: > `var(view.--name)` is got from `view.style()` and `var(--name)` from `sublime.ui_info()`, all values resolved. > As for `view.`...

While generally it is recommended to use the settings to set your preferred default, I can understand that it may be useful, after configuring the options via the commands, to...

I plan to target specifically the settings: `group_bytes_by_bits` and `bytes_per_line`. Please let me know if there are other settings that make sense. I wasn't planning on it, but maybe `inspector_endian`...