| Age | Commit message (Collapse) | Author |
|---|
|
Fixes #8337.
|
|
|
|
The behavior changed and now it actually makes sense.
Fix #8385.
|
|
This also changes its license to MIT along the way.
|
|
This updates the VTE crate to the latest version, bringing in a nice SGR
performance boost.
Co-authored-by: Kirill Chibisov <contact@kchibisov.com>
|
|
This should fix the screenshot image on crates.io.
https://github.com/rust-lang/crates.io/issues/5318
|
|
|
|
Changing block selection to regular semantic one doesn't feel intuitive,
thus don't switch to it when user has control pressed.
|
|
The implementation is the same as CSI Ps Z, but forward.
|
|
This fixes an issue with daemon mode where the first spawned window
would not use the window options passed to the `create-window`
subcommand, but would instead use the options passed during creation of
the original daemon.
Closes #8371.
|
|
Fixes double input on X11 after update to 0.30.6.
|
|
Fixes #8268.
|
|
While this doesn't change much with how parsers are implemented, it
improves consistency with how key release is handled.
|
|
This fixes a GitHub security alert about hashbrown, which has no
significant impact on Alacritty but still seems wise to fix since it's
so simple.
|
|
|
|
YAML import migration was already properly ignoring nonexistent imports,
it was only missed for TOML ones.
Fixes #8330.
|
|
|
|
|
|
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.
|
|
|
|
|
|
This fixes a couple issues with hint highlight invalidation, which would
cause hints to lose their underline highlight despite the terminal
itself not having changed since the highlight started.
Closes #8270.
|
|
|
|
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.
|
|
The pipe was not using O_CLOEXEC, so it was leaked into the child.
Fixes #8249.
|
|
|
|
This patch adds a daemon mode to Alacritty which allows starting the
Alacritty process without spawning an initial window.
While this does not provide any significant advantage over the existing
behavior of always spawning a window, it does integrate nicer with some
setups and is a pretty trivial addition.
|
|
This changes the behavior of inline search from only accepting direct
key inputs, to also accepting IME and paste. The additional characters
are still being discarded, matching the existing behavior.
This also fixes an issue where inline search wouldn't work for
characters requiring modifiers, since the modifier press was interpreted
as the search target instead.
Closes #8208.
|
|
Use `end` of the cursor to draw a `HollowBlock` from `start` to `end`.
When cursor covers only a single character, use `Beam` cursor instead
of `HollowBlock`.
Fixes #8238.
Fixes #7849.
|
|
Fixes #8230.
|
|
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.
|
|
Avoid collisions with IMEs by using ctrl+shift+o. ctrl+shift+u is bound
to open unicode input in a lot of IMEs by default meaning that users
won't ever see the url hints UI.
|
|
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.
|
|
The first line is not really useful for the user, so move it to the
bottom.
|
|
This patch allows running `alacritty migrate` to automatically apply
configuration changes made to the TOML format, like moving `ipc_socket`
to `general.ipc_socket`.
This should reduce the friction of moving around individual options
significantly, while also persisting the format of the existing TOML
file thanks to `toml_edit`.
The YAML migration has been simplified significantly to only switch the
format of the file from YAML to TOML. The new TOML features are used for
everything else.
|
|
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.
|
|
Currently when the cursor colors are requested for the default cursor
color, Alacritty always responds with #000000. Since this is most likely
incorrect, this response is misleading.
Realistically there's very little reason why any application would need
to know the color of the (often dynamically changing) default cursor. So
instead of always reporting an incorrect black value, this patch just
stops reporting values unless the cursor color was explicitly changed.
Closes #8169.
|
|
This also fixes the escaping in alacritty(5) page.
|
|
|
|
|
|
|
