| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
| |
| |
| | |
Make sure buffer-close waits for the document to finish its writes.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The way that document writes are handled are by submitting them to the
async job pool, which are all executed opportunistically out of order. It
was discovered that this can lead to write inconsistencies when there
are multiple writes to the same file in quick succession.
This seeks to fix this problem by removing document writes from the
general pool of jobs and into its own specialized event. Now when a
user submits a write with one of the write commands, a request is simply
queued up in a new mpsc channel that each Document makes to handle its own
writes. This way, if multiple writes are submitted on the same document,
they are executed in order, while still allowing concurrent writes for
different documents.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Support different kinds of underline rendering (updated)
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| | |
Co-authored-by: Omnikar <omkar.subramaniam@icloud.com>
|
| | | |
|
| | |
| |
| |
| | |
colors
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Underline styles are mutally exclusive and overwrite each other.
Therefore implementing as an modifier lead to incorrect behaviour
when the underline style is overwritten.
For backwards compatability the "underline" modified is retained (but
deprecated). Instead the "underline_style" and "underline_color"
optios should be used to style underlines.
|
| | |
| |
| |
| |
| |
| |
| | |
The cxterminfo crate has been used over popular alternatives
like `term` since it supports querying for extended capabilities
and also for it's small codebase size (which will make it easy
to inline it into helix in the future if required).
|
| | | |
|
| | |
| |
| |
| | |
Add underline field to doctests, and fix bugs
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds four new modifiers that can be used in themes:
- undercurled
- underdashed
- underdotted
- double-underline
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
as the default file picker (#4334)
Skip searching .git in global search, similar to how file picker skips listing files in .git.
|
| | |
| |
| | |
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| | |
| |
| | |
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| | |
| |
| | |
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Instead of repeatedly checking if it is in_bounds, calculate the
max_indent beforehand and just loop. I added a debug_assert to "prove"
that it never tries drawing out of bounds.
|
| | |
| |
| |
| |
| |
| | |
Better performance, and otherwise very long lines with lots of tabs
will wrap around the u16 and come back on the other side, messing up
the beginning skip_levels.
|
| | | |
|
| | |
| |
| |
| |
| | |
Before things would be cast to u16 earlier than needed, which would
cause problems for insanely long lines (longer than 2^16 ~ 65 thousand)
|
| | |
| |
| |
| |
| |
| |
| | |
Also changes workspace diagnostic picker bindings to <space>D and
changes the debug menu keybind to <space>g, the previous diagnostic
picker keybind. This brings the diagnostic picker bindings more in
line with the jump to next/previous diagnostic bindings which are
currently on ]d and [d.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
palettes (#4221)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Info logs don't show up in the log file by default, but this line
should: failures to load tree-sitter parser objects are useful errors.
A parser might fail to load it is misconfigured
(https://github.com/helix-editor/helix/pull/4303#discussion_r996448543)
or if the file does not exist.
|
| | |
| |
| |
| |
| |
| |
| | |
The debug assertion that document diagnostics are sorted incorrectly
panics for cases like `[161..164, 162..162]`. The merging behavior
in the following lines that relies on the assertion only needs the
input ranges to be sorted by `range.start`, so this change simplifies
the assertion to only catch violations of that assumption.
|
| | |
| |
| | |
Co-authored-by: Michael Davis <mcarsondavis@gmail.com>
|
| | | |
|
| | |
| |
| | |
Co-authored-by: Wojciech Kępka <wojciech.kepka@softax.pl>
|
| | |
| |
| | |
Co-authored-by: Wojciech Kępka <wojciech.kepka@softax.pl>
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- treat `restrict`/`_Atomic` like `const`/`volatile` => @keyword.storage.modifier
- highlight `unsigned int` as builtin => @type.builtin
- recognize `static_cast` and friends => @keyword
- `template` is a kind of entity like `typename` => @keyword.storage.type
- many declaration modifiers have nothing to do with storage/types
(explicit, friend, access specifiers, inline in C++) => @keyword
- fix floats highlighted as integer => @constant.numeric
|
| | | |
|
