-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Font-lock facts and built-in variables #47
Comments
We can add a list of all built-in facts, but it's going to be huge, and how should we deal with variable facts, e.g. For completion, I'd not rely upon a built-in list of facts, but rather parse the output of |
The problem is that if you have a If you think this list is huge I guess you haven't seen the built-in lists in |
@bbatsov I don't think that we'll be able to re-use the list compiled for fontification for completion. Fontification must use regular expressions to deal with variable fact names (e.g. |
I think we can generate the regexp from the list of built-in vars/facts and use the list itself as a completion source. |
@bbatsov Sounds good. I'll look into it. |
I think it would be great if we font-locked facts and built-in variables differently from user-defined variables to highlight their special status. A list of them is available here. In
ruby-mode
we usefont-lock-builtin-face
for those, although I guess we can introduce a different face inpuppet-mode
.They'll also be a great candidate for completion when we get to the
completion-at-point-functions
support.The text was updated successfully, but these errors were encountered: