This makes it possible to look through the command history based on a
prefix, which can make it much faster to find what we want when we know
what it starts with!
To use it, simply type the prefix before looking through command history
with Up/Down arrow keys.
The non-prefixed history works just like before, although now the state
resets when the prompt is modified.
Previously unnecessary/deprecated diagnostic tags replaced the highlight
for the severity of a diagnostic. This could cause either the severity
or unnecessary/deprecated scopes to disappear when diagnostic ranges
overlapped though. Plus the severity highlight can be interesting in
addition to the unnecessary/deprecated highlight.
So this change separates the unnecessary and deprecated highlights from
the severity highlights, so each is merged separately and when they
overlap, the highlights are combined.
Without a serializer, we drop the custom alphabet when making config
modifications like with `:set`. For example before this commit,
`:set mouse false` would reset a custom alphabet to the default.
This patch merges the last child of a container node to the parent. This
avoids the bug where uneven spaced Views would be created. To reproduce:
1. `vsplit`
2. `split`
3. `quit`
4. `vsplit`
With this patch the bug cannot be seen anymore.
`LLVM v18.0.0` changed the name here: llvm/llvm-project#69264
Current users of `lldb-vscode` not able to upgrade will have to create a
symlink so that `lldb-dap` links to `lldb-vscode`.
BREAKING CHANGE: debugger looks for `lldb-dap` rather than `lldb-vscode`
closes: #9964
* Use any-of instead of match in yaml injections
Go back to original intent when this code was first written now that the
tree-sitter version used supports any-of?.
* yaml/injections: Add injection for Buildkite
Buildkite uses `command` (`commands` is an alias) to define the
command(s) to run for the step.
* add jump-label styling for base16_transparent theme
* keep the change consistent with other themes from base16 family
* update jump-labels color to blue and make them bold
Prior to this change, every integration test which wanted its line
endings to be handled transparently across platforms, i.e. test with
the same input that has its platform's line feed characters, converting
the line endings was up to each individual test by calling the
`platform_line` helper function. This significantly increases the amount
of boilerplate one has to copy between all the tests.
However, there are some test cases that need to exert strict control
over the exact input text without being manipulated behind the scenes by
the test framework.
So, with this change, the line feed conversions are factored into
the `TestCase` struct. By default, line endings of the input text
are converted to the platform's native line feed ending, but one can
explicitly specify in their test case when the input text should be left
alone and tested as is.