aboutsummaryrefslogtreecommitdiffstats
path: root/runtime/queries/bash/highlights.scm
Commit message (Collapse)AuthorAgeFilesLines
* feat(bash): highlight arguments of trap and kill builtin commandsOmar Valdez2025-12-081-12/+24
|
* feat(bash): remove unnecessary capturesOmar Valdez2025-12-081-6/+0
| | | | | | - Bash does not have boolean values and the builtin `true` and `false` commands are already covered by another capture. - The grammar has a `number` node and it's already captured.
* fix(bash): highlight shebang also when spacedÉric NICOLAS2025-06-091-1/+1
| | | | | | | | | | | | | | | | | | | | | This commit aligns the shebang highlighting in bash syntax to what the Linux kernel will recognise as a valid shebang construct. In summary, the kernel will accept both headers: #!/usr/bin/env lua #! /usr/bin/env lua The second one is quite prominently used throughout documentation online, such as on Wikipedia's page for Shebang (Unix) [1]. Some sources are adamant it wouldn't be supported at a kernel level, but it looks to me, upon closer inspection of the current kernel code [2], that it is indeed quite evidently valid. It'll simply skip over to the first character that's neither a space 0x20 nor a tab 0x09. [1] https://en.wikipedia.org/wiki/Shebang_(Unix) [2] https://github.com/torvalds/linux/blob/ec7714e4947909190ffb3041a03311a975350fe0/fs/binfmt_script.c#L44-L71
* feat(bash): highlight variable argument for `printf -v`Omar Valdez2025-05-241-0/+11
|
* feat!: drop modules, general refactor and cleanupChristian Clason2025-05-121-0/+261