-
Notifications
You must be signed in to change notification settings - Fork 142
Conversation
'name': 'punctuation.definition.entity.begin.html' | ||
'2': | ||
'name': 'entity.name.entity.other.html' | ||
'end': '(;)' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parentheses aren't required around this: you can just match the 0th capture instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @50Wliu and thanks for the suggestions. How do you think it should be? I don't know if I understand what you say.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'end': ';'
'endCaptures':
'0':
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @MaximSokolov. Fixed in the last commit.
What does this fix/add? Is there a reason we can't keep the existing |
@50Wliu The existing |
I'm investigating what's the latest on this PR, as I want to contribute few attributes to be suggested (they're not present in your pull btw) and these commits might overlap with what I want to add. Half year has passed since latest action! |
It looks like I dropped the ball on this PR. At this point it needs to be rebased. I still am not convinced that we need to switch to a begin/end model as a capture can simply be added for the semicolon. |
@revelt If you want you can send me a PR to add more entities. |
Ok, here's what I'm proposing: 'captures':
'1':
'name': 'punctuation.definition.entity.html'
'2':
'name': 'entity.name.entity.other.html'
'3':
'name': 'punctuation.terminator.statement.html' # or something else, iunno
'match': '(&)([a-zA-Z0-9]+|#[0-9]+|#x[0-9a-fA-F]+)(;)'
'name': 'constant.character.entity.html' Does that work out for what autocomplete-html needs? |
Thanks for your proposal @50Wliu . The issue with your solution is that your |
Ok, I see what you're saying now. Your solution looks like the way to go then. |
@50Wliu What is the next step? Should I rebase? |
Yes please. |
ee31e2e
to
2868437
Compare
@50Wliu Rebase done. 🍨 |
Thanks, and sorry for the delay! |
Thanks for merging 😸 |
Related to atom/autocomplete-html#14