16 commits

Author	SHA1	Message	Date
Omar Valdez	466da58e5b	feat(css): highlight square brackets	2024-04-26 21:40:20 -04:00
Jaehwang Jung	998b230a77	feat(highlights)!: keyword @type.qualifier → @keyword.modifier	2024-03-16 20:51:16 +08:00
ObserverOfTime	505a0e74cb	fix(css): make the highlights more sensible	2024-01-19 16:58:37 +01:00
Pham Huy Hoang	57a8acf0c4	chore: query formatting	2024-01-19 16:58:37 +01:00
Christian Clason	1ae9b0e455	feat!: align standard captures with upstream ... Problem: Sharing highlight queries with upstream tree-sitter and Helix is difficult. Solution: Where reasonable, use capture names in tree-sitter's standard list or Helix's Atom-style hierarchy. Specifically: * tree-sitter "standard capture names" (3f44b89685/highlight/src/lib.rs (L20-L72)): - `@parameter` -> `@variable.parameter` - `@field` -> `@variable.member` - `@namespace` -> `@module` - `@float` -> `@number.float` - `@symbol` -> `@string.special.symbol` - `@string.regex` -> `@string.regexp` - `@text.*` -> `@markup.*` (`strong`, `italic`, `link`, `strikethrough`; with exceptions; see below) - `@text.title` -> `@markup.heading` - `@text.literal` -> `@markup.raw` - `@text.reference` -> `@markup.link` - `@text.uri` -> `@markup.link.url` (in markup links) - `@string.special` -> `@markup.link.label` (non-url links) - `@punctuation.special` -> `@markup.list` (markdown lists only; move subitems from `@text.todo`) * Helix captures (https://docs.helix-editor.com/master/themes.html#syntax-highlighting): - `@method` -> `@function.method` - `@method.call` -> `@function.method.call` - `@text.{todo,warning,note,danger}` -> `@comment.{error,warning,hint,info,todo}` - `@text.diff.{add,delete,}` -> `@diff.{plus,minus,delta}` - `@text.uri` -> `@string.special.url` (outside markup) - `@preproc` -> `@keyword.directive` - `@define` -> `@keyword.directive`(`.define`?) - `@storageclass` -> `@keyword.storage` - `@conditional` -> `@keyword.conditional` - `@debug` -> `@keyword.debug` - `@exception` -> `@keyword.exception` - `@include` -> `@keyword.import` - `@repeat` -> `@keyword.repeat` * cleanup - remove some redundant `@conceal` (but still allow it for conceal-only patterns) - remove obsolete `@error` (syntax linting is out of scope for this repo) - sort, cleanup capture list in `CONTRIBUTING.md`	2024-01-19 16:58:37 +01:00
Riley Bruins	2a5f6c9eb7	fix(css): tweak operator keyword highlights	2023-11-22 19:11:45 -05:00
Pham Huy Hoang	107e61afb7	refactor: Remove all (ERROR) @error captures ... As discussed in PR#5421, capturing `@error` is inconsistent, requiring deep nesting (or priority) in order to correctly have red backgrounds to it. Some queries has this capture, some don't. For consistency purposes, removing all of them is more preferable. For re-enabling error, either add `(ERROR) @error` or `(ERROR _ @error)` to your custom queries.	2023-10-25 18:18:50 +02:00
Amaan Qureshi	85330918f0	perf: remove match where possible	2023-04-21 18:24:17 -04:00
ObserverOfTime	c2d9cf9926	highlights(css): use more specific groups	2022-11-26 13:17:51 +02:00
Lewis Russell	37398c7d68	feat(spell): support more languages	2022-09-26 13:47:12 +01:00
Stephan Seitz	7a3ecabf56	highlights(css): fix property highlighting ... Apply fix as suggested by https://github.com/binhtran432k Fixes #3395 Co-authored-by: Trần Đức Bình <binhtran432k@users.noreply.github.com>	2022-09-10 13:02:07 -07:00
Stephan Seitz	c7e8f76f3c	Fix invalid node type in CSS queries	2021-03-16 18:52:43 +01:00
Steven Sojka	ce43dbf54c	fix(queries): use vim-match for non lua regexes	2020-08-16 18:31:56 +02:00
TravonteD	0f836e0602	refactor: use newly introduced consolidated syntax	2020-06-20 09:03:39 -04:00
TravonteD	37f9866f66	- #76 update the predicate syntax for ruby and css	2020-06-11 10:38:19 -04:00
TravonteD	58f5bdbe01	Add css highlight queries	2020-06-02 15:11:35 -04:00