summaryrefslogtreecommitdiffstats
path: root/queries/ruby
Commit message (Collapse)AuthorAgeFilesLines
* feat(ruby): detect shebang directiveJerome Dalbert2024-09-171-0/+5
|
* feat(ruby): improve identifiers highlightingJerome Dalbert2024-09-121-3/+6
|
* feat(ruby): string/punctuation highlight improvementsRiley Bruins2024-08-261-10/+17
|
* fix(ruby): highlight "&." as `@punctuation.delimiter` (#6887)Wadii Hajji2024-07-081-0/+1
|
* feat(ruby): highlights for special methods (#6735)Pete Matsyburka2024-07-081-3/+8
|
* feat: more `@keyword.type` capturesRiley Bruins2024-05-011-1/+2
|
* refactor(format): drop extra indentation for fieldPhạm Huy Hoàng2024-03-212-25/+20
|
* feat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`Jaehwang Jung2024-03-161-2/+2
|
* feat(highlights)!: enforce documented captures (#6232)Christian Clason2024-03-031-3/+4
| | | | | | | | | | | | | | | Problem: Allowing undocumented "secret" (sub)captures makes it harder to write comprehensive colorschemes and catch inconsistent captures. Solution: Only allow captures listed in CONTRIBUTING.md. Add useful (cross-language) subcaptures and drop language-specific or too niche ones. Follow-up: Adding further `*.builtin` captures and changing queries to use them. Language-specific subcaptures should instead be added in user config or a custom language plugin.
* feat(format-scripts): linewrap predicates再生花2024-02-231-1/+2
| | | "format-ignore".kick()
* fix(highlights): improve member/property distinctionObserverOfTime2024-01-191-2/+2
|
* fix(highlights): improve consistencyObserverOfTime2024-01-191-1/+1
|
* chore: query formattingPham Huy Hoang2024-01-193-182/+253
|
* feat!: align standard captures with upstreamChristian Clason2024-01-191-20/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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" (https://github.com/tree-sitter/tree-sitter/blob/3f44b896852eb7daaa6df4fb778c9bb52c70c815/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`
* feat(locals)!: switch to upstream capturesChristian Clason2024-01-191-23/+23
|
* refactor: Remove all `(ERROR) @error` capturesPham Huy Hoang2023-10-251-2/+0
| | | | | | | | | | | | 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.
* refactor: replace some match & vim-match usagesObserverOfTime2023-08-231-3/+3
|
* fix(directive): make downcase work on capturesChristian Clason2023-08-121-2/+1
|
* chore(injections)!: update injection syntax to 0.9Pham Huy Hoang2023-08-121-5/+8
| | | | | | | | | Since 0.9, @lang syntax is still available as fallback but will soon be deprecated. Because of that, new syntax should be adopted once 0.9 becomes the baseline requirements for nvim-treesitter - update health check - update doc
* queries/*/highlights.scm : remove `@spell` for stringsShellCode332023-08-071-2/+0
|
* fix(ruby): bare_symbol should be @symbolSerhii Budnik2023-04-171-1/+1
|
* fix(ruby): then blocks should not be `@conditional`, just "then"Trey Wood2023-03-311-6/+1
|
* use indent.X syntax for captures and properties of set directivesGeorge Harker2023-03-241-4/+4
| | | | | | | | update CONTRIBUTING.md adjust indents for bass fix doc capture comment
* feat: add `@comment.documentation` where applicableAmaan Qureshi2023-03-051-3/+20
|
* refactor(ruby): move keywords appropriatelyAmaan Qureshi2023-03-031-6/+21
|
* Update indents.scmCameron2023-01-091-2/+1
|
* Update indents for RubyCameron2023-01-061-0/+2
| | | Add `rescue` and `ensure` as a @branch captures for ruby
* injections: add more regex injectionsObserverOfTime2022-11-271-0/+2
|
* highlights(ruby): fix capturesObserverOfTime2022-11-261-4/+5
|
* Add global variable highlightingCameron2022-09-101-0/+1
|
* feat(spell): upstream spell queries from spellsitterLewis Russell2022-09-061-0/+2
|
* fix(ruby): indent of brackets & parensZheng Piaodan2022-08-131-2/+0
|
* fix(ruby): indent parenthesized_statementsZheng Piaodan2022-08-131-0/+1
|
* Split func/method definition from calls in several programming language querieslfenzo2022-08-031-1/+1
|
* fix: add more indentations for ruby (#3139)Eric Zheng (PiaoDan)2022-07-091-0/+2
|
* Update highlights.scmCameron2022-06-241-0/+2
| | | | | | Adds `undef` and `redo` keywords. https://docs.ruby-lang.org/en/2.4.0/syntax/miscellaneous_rdoc.html#label-undef https://docs.ruby-lang.org/en/2.4.0/syntax/control_expressions_rdoc.html#label-redo+Statement
* Add more indentationsNick Pezza2022-03-121-0/+5
|
* Dedent on end in ruby filesNick Pezza2022-03-121-0/+7
| | | | Fixes #2554
* Update queriesSantos Gallegos2021-12-221-3/+2
| | | | | - Don't use the old form for predicates - Update some invalid queries
* Add Operators for RubyCameron2021-11-111-5/+38
| | | | | | | Many operators were missing from ruby, so, I added them. Additionally, with string interpolation (`"#{xxx}"`), the closing `}` was being matched to `punctuation.bracket` instead of `punctuation.special`, so I fixed that too. I didn't see any further details about how to contribute, so if I've overlooked anything, I'll be happy to add it.
* Fix instance and singleton method locals for RubyYorick Peterse2021-08-091-1/+2
| | | | | | | | | | | | | | | Ruby singleton methods (`def x.y ... end`) weren't covered in the list of locals. In addition, instance methods didn't support names that are capitalised (`def Integer ... end`). This commit ensures that both instance and singleton methods are supported, and that both support identifiers and constants as their names. This ensures that all following examples are covered: def foo; end def FOO; end def self.bar; end def self.BAR; end
* feat(keywords) merge return and yield into keyword.return groupantonk522021-07-041-4/+1
|
* feat(keywords) add keyword.return & keyword.yieldantonk522021-07-041-2/+8
|
* downcase! directive to use with ruby injectionsderekstride2021-06-041-0/+6
| | | | | | | | | | | | | | | | | ``` (#downcase! "language") ``` downcase! will ensure the metadata value for the specified key will be downcased. If the value is a node, it will downcase the text specified by the node. ``` (#downcase! @node "key") ``` You can also namespace the key with a specific capture, similar to how you can call `(#set! @node "key" "value")`
* Revert "Comment: use `@combined` to create just one tree per buffer (#1252)"Santos Gallegos2021-05-071-1/+1
| | | | This reverts commit 4a7a713c527f57c355bc817f16fc6d955b8cce9b.
* Comment: use `@combined` to create just one tree per buffer (#1252)Santos Gallegos2021-04-281-1/+1
| | | | | | | | | | | | * Comment: use `@combined` to create just one tree per buffer There is no need to create a tree per line/block for comments. Should fix https://github.com/nvim-treesitter/nvim-treesitter/issues/1251 * Add injections for scss * Fix jsonc * Combine jsdoc
* Indent Ruby singleton classesImobach González Sosa2021-04-171-0/+1
|
* folds support and somewhat better indents for rubyIvo Dancet2021-03-152-0/+26
|
* Add comment parser to highlight comment tags (#893)Santos Gallegos2021-03-121-0/+1
| | | Closes #236
* [highlights] Add TSSymbol highlight groupDennis B2021-03-041-1/+1
| | | | | | | | | | | | | | Addresses issue #892 Ruby and Dart literal symbols will now be highlighted by the new TSSymbol highlight group, which itself will, by default, link to the Vim Identifier highlight group. Vim theme authors can then set their TSSymbol colors. Symbol highlighting can apply to a number of languages as noted in the following Wikipedia page: https://en.wikipedia.org/wiki/Symbol_(programming) Not just for Ruby and Dart.