| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
| |
This fixes an issue where Alacritty would crash when trying to open a
new tab on macOS while having decorations disabled.
Co-authored-by: Christian Duerr <contact@christianduerr.com>
|
|
|
|
|
|
|
|
|
|
| |
Make `Alt` send `ESC` for unicode input the way it's done for ASCII.
Previously it was disabled because of macOS, however on macOS we're
using the `option_as_alt` setting, which solves the original issue.
The `Alt` prefixing is still disabled for the unicode strings, like
when they come from the compose input.
Fixes #7852.
|
|
|
|
|
| |
On Windows some key combinations for regular text input, like Ctrl+1
don't have any text attached, so they were generating the kitty escape
sequence even when they shouldn't.
|
|
|
| |
Closes #7778.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Fixes #7753.
|
| |
|
| |
|
| |
|
|
|
| |
Fixes #7665.
|
|
|
| |
Closes #7680.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Originally kitty defined that functional keys, which are not encoded
by default, like `Pause` should be encoded with `CSI u`. However
the specification was clarified and now it says that terminal
may ignore that part. Given that Alacritty tries to follow xterm/urxvt
when it comes to bindings, CSI u bindings are not send for consistency
reasons.
This also brings back F13-F20 bindings used by Alacritty in 0.12.3, as
well as explicitly defines `NumpadEnter` like it was before.
Closes #7623.
|
|
|
|
|
|
|
|
| |
This has a side effect that we'll have text reported for Alt+Shift+T
and similar, but only C0/C1 should be excluded and Alt+Shift+T is
emitting neither, thus regular `T` will be reported.
Fixes #7657.
|
|
|
|
|
|
| |
Sextants are similar to quadrants and should align with them and
other box drawing, thus use builtin font to align them properly.
Part-of: #7422.
|
|
|
| |
Closes #7592.
|
|
|
|
|
|
|
| |
Patch 5685ce8bf changed the allowed values of the `debug.renderer` enum,
prohibiting the usage of `_` in the `Gles2Pure` variant. This patch
updates the documentation to correct for that.
Co-authored-by: Kirill Chibisov <contact@kchibisov.com>
|
| |
|
|
|
|
| |
This should help with broken YAML configurations by throwing nulls
away, which are not representable in toml.
|
|
|
| |
Closes #7511.
|
|
|
|
|
|
|
| |
This fixes an issue with the default `SerdeReplace` implementation where
it would never recurse through options but always replace the entire
option with the new value.
Closes #7518.
|
|
|
|
|
|
|
| |
The toml migration introduced a regression which stopped numbered key
binding's from working. This patch implements the required number type
to make things work again.
Fixes #7527.
|
|
|
| |
Fixes #7470.
|
|
|
|
|
| |
Also fix the wrong ordering of base and shifted keys.
Fixes #7492.
|
|
|
|
|
|
| |
This broke unintentionally due to routing paste-like input
via paste function.
Fixes #7476.
|
| |
|
|
|
|
| |
Fixes #7506.
|
|
|
|
| |
Fixes #7475.
|
|
|
| |
With MSRV 1.70, std now contains the necessary parts.
|
|
|
| |
Fixes #7473.
|
|
|
|
|
|
|
|
|
| |
While this doesn't handle releases with multiple identical modifiers
pressed, the release can't work reliable anyway, since one modifier
could be pressed before focusing the window, thus tracking modifiers
based on the keysym values won't work as it was suggested by kitty
author.
Links: https://github.com/kovidgoyal/kitty/issues/6913
|
|
|
| |
Fixes #7195.
|
|
|
|
|
|
| |
By default `Alt` is not a real `Alt` on macOS, so we shouldn't treat
it as a modifier.
Fixes #7443.
|
|
|
| |
Fixes #7438.
|
| |
|
|
|
|
|
|
| |
The regression was added due to `y` coordinate in OpenGL differs to
`y` inside the damage rectangles.
Fixes: 40160c5d (Damage only terminal inside `alacritty_terminal`)
|
|
|
|
|
|
|
|
|
| |
When the key doesn't have textual representation we shouldn't emit
the text for them, since they are processed via bindings.
Also, fix the logic to handle named keys with disambiguate without
special modes/modifiers.
Fixes #7423.
|
|
|
|
|
|
|
| |
We should ensure that the `Shift` is actually pressed when trying to
prefer regular bindings instead of the ones if we had Shift applied.
Fixes: 500b696ca8ed (Prefer exact matches for bindings in mouse mode)
Fixes #7415.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
| |
Fixes #7413.
|
| |
|
|
|
|
|
| |
Some hardware is just bad.
Fixes #7404.
|
|
|
| |
We have the same policy with Shift for numbers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When setting cursor area, the popup will be placed either above or
below not obscuring the supplied region, however we were still
offsetting line with `+1` putting the cursor at the bottom of the line,
and given that area is from the top-left corner, the wrong area
was marked for not being obscured.
It was also discovered that some compositors, like GNOME, position
IME in the bottom right corner of the supplied region, which is wrong,
but it renders IME popup not very useful, since it's far away from
the place it should be, thus try to not obscure just a few characters
near the cursor.
Given that X11 doesn't support area setting, it uses the old logic
with offsetting.
Co-developed-by: lilydjwg <lilydjwg@gmail.com>
Signed-off-by: lilydjwg <lilydjwg@gmail.com>
|
|
|
|
|
|
| |
Font size could change without changing the cell dimensions, like
becoming slightly higher/wider.
Fixes: 40160c5d (Damage only terminal inside `alacritty_terminal`)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
Iterate over points in line instead of drawing it right away
and then finding it in the buffer.
Fixes: 4a26667060 (Use builtin font to draw powerline symbols)
|