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

fix Markdown list highlighting #2401

Merged
merged 1 commit into from
May 7, 2022
Merged

Conversation

ChrHorn
Copy link
Contributor

@ChrHorn ChrHorn commented May 4, 2022

This should fix #1597

I did it according to the current docs. Question is, should we

  1. keep the 2 different styles for ordered/unordered
  2. add markup for list text itself

@the-mikedavis
Copy link
Member

What would you think about markup.list.ordered/markup.list.unordered similar to the HTML phrases for these? I don't mind numbered and unnumbered though.

@the-mikedavis
Copy link
Member

for the questions:

  1. I like the distinction between ordered and unordered. A theme can define just markup.list as a fallback so it doesn't have to theme them differently if it doesn't want.
  2. I don't mind not theming the item text. I don't really see a scenario where it would be useful. But I probably wouldn't argue against it.

@ChrHorn
Copy link
Contributor Author

ChrHorn commented May 4, 2022

What would you think about markup.list.ordered/markup.list.unordered similar to the HTML phrases for these? I don't mind numbered and unnumbered though.

Yes, that would be a good idea. The spec uses ordered list and bullet list but I would prefer unordered.

@ChrHorn
Copy link
Contributor Author

ChrHorn commented May 6, 2022

Reanaming should not cause any issues. There was only one existing theme that used these fields. Didn't see it on external repos either.

@archseer
Copy link
Member

archseer commented May 6, 2022

Why the rename though? I tried keeping the same scopes as textmate / sublime themes https://www.sublimetext.com/docs/scope_naming.html#markup

@ChrHorn
Copy link
Contributor Author

ChrHorn commented May 6, 2022

Makes sense, consistency with that spec is more important. Have reverted the renaming. Should be ready to merge.

@archseer archseer merged commit b38c268 into helix-editor:master May 7, 2022
@ChrHorn ChrHorn deleted the markdown-list branch May 7, 2022 05:31
fourlexboehm pushed a commit to fourlexboehm/helix that referenced this pull request May 12, 2022
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

Successfully merging this pull request may close these issues.

Markdown highlighting issues
3 participants