| Age | Commit message (Collapse) | Author |
|---|
|
This is only an update to the development version and does not represent
a stable release.
|
|
The implementation is the same as CSI Ps Z, but forward.
|
|
This patch fixes an issue where the semantic vi motion commands
`SemanticRight` and `SemanticLeft` were not behaving as expected when a
fullwidth character was used as a semantic character.
Closes #8314.
|
|
This patch applies all major and minor version bumps, with the exception
of `unicode-width` since it will need to be handled separately for
Unicode version 16.
|
|
This fixes an issue with hints where it was possible that the terminal
content of highlighted hints changed between the highlighted hint update
and the activation of the hint.
This patch always validates the hint's text content against the hint
itself to ensure that the content is still valid for the original hint
which triggered the highlight.
Closes #8277.
|
|
alacritty_terminal was pulling `serde` via vte even though
serde feature was disabled.
|
|
This is only an update to the development version and does not represent
a stable release.
|
|
This reverts commit 5dca7a85e7d8e98f8e770c17af8efb442c2277d0.
|
|
This fixes issues in width calculation for symbols added in Unicode
version 16.
Since the upstream unicode-width crate has not been updated yet, this
makes use of the temporary unicode-width-16 version to support Unicode
16 with Alacritty 0.14.0.
|
|
This fixes an issue where hints highlighted by vi or mouse cursor would
produce an underline on the incorrect line since the highlights only
store the initial match boundaries without accounting for new content
scrolling the terminal.
To accurately invalidate the hint highlights, we use existing damage
information of the current frame. The existing logic to damage hints for
the next frame to account for removal has been changed, since the hints
would otherwise be cleared immediately. Instead we now mark the terminal
as fully damaged for the upcoming frame whenever the hints are cleared.
Closes #7737.
|
|
|
|
This will prevent issues when `setup_env` from `alacritty_terminal` will
remove potentially useful variables for users of the library.
Fixes #8202.
|
|
Some users struggle with TOML, since root options must always be at the
top of the file, since they're otherwise associated with the last table.
To avoid misunderstandings, all root-level fields have been removed. A
new `general` section was added to allow housing configuration options
that do not fit into any more specific groups.
Closes #7906.
|
|
Semantic escape characters occupying two two grid cells were always
skipped over, making it impossible to have functional fullwidth
characters as part of semantic escape characters.
This patch fixes this by only skipping over fullwidth spacer cells,
rather than skipping those cells entirely.
Closes #8188.
|
|
|
|
|
|
|
|
This fixes an issue where an inline search in the left direction would
incorrectly assume that the first cell searched would not contain the
`WRAPLINE` flag, causing the second search for the match end to
terminate prematurely.
Fixes #8060.
|
|
|
|
This was not a _real_ violation and was _expected_, though for rust
to not complain clone FD properly...
|
|
This patch fixes an issue with signal handling where Alacritty would
permanently create one signal handling FD for each alacritty window
created by an instance. This FD was never released, causing a leak of
the FD.
Closes #7983.
|
|
Closes #7886.
|
|
|
|
This is only an update to the development version and does not represent
a stable release.
|
|
|
|
Winit explicitly states that the window is not focused by default and
the `Focused` event will deliver the state later on.
Also start adding notable changes to alacritty_terminal in its own
CHANGELOG.
Closes #7866.
|
|
|
|
Closes #7778.
|
|
This bumps all dependencies that can be updated without introducing a
build failure.
|
|
This fixes an issue where the `Select` action for hyperlink escape text
would select the entire line, instead of selecting only the hyperlink
itself.
It also changes the way hyperlinks with the same ID are highlighted,
removing the restriction of being on consecutive lines and instead
highlighting all visible cells that correspond to the matching
hyperlink.
Closes #7766.
|
|
117719b3 removed the extra call for TIOCSWINSZ, however the initial
`openpty` call itself did not set the pixel size, which caused issues
with some clients.
|
|
Fixes #7753.
|
|
|
|
|
|
|
|
This fixes an issue where a scrolling region that does not start at the
top of the screen would still rotate lines into history when scrolling
the content "upwards".
|
|
|
|
The openpty call already performs it, thus no need to call it one more
with the exact same size since it confuses some applications.
|
|
This is only an update to the development version and does not represent
a stable release.
|
|
Closes #7680.
|
|
|
|
Closes #7587.
|
|
Authored-by: James McCoy <jamessan@jamessan.com>
|
|
|
|
|
|
This is only an update to the development versions and does not
represent a stable release.
|
|
The protocol enables robust key reporting for the applications, so
they could bind more keys and the user won't have collisions with
the normal control keys.
Links: https://sw.kovidgoyal.net/kitty/keyboard-protocol
Fixes #6378.
|
|
The DECRQM uses `p` to query, but the reply uses `y`.
Fixes #7397.
|
|
Update dependencies with `cargo update` as well as do explicit update
of winit, crossfont, and regex-automata.
|
|
The damage tracking was including selection and vi_cursor which were
rendering viewport related, however all the damage tracking inside
the `alacritty_terminal` was _terminal viewport_ related, meaning that
it should be affected by `display_offset`.
Refactor the damage tracking so `alacritty_terminal` is only tracking
actual terminal updates and properly applying display offset to them,
while `alacritty` pulls this damage into its own UI damage state.
Fixes #7111.
|
