Age | Commit message (Collapse) | Author |
|
|
|
|
|
There's no reason why we should ever manually set the terminal to not be
dirty, since this can lead to a lot of other logic being affected. This
also does not have any benefit and was likely added in the event loop
rework as a bug (probably should have been dirty = true).
|
|
Fixes resize regression from 15cc07c069b09f109ed18fb94e02e9650be7fa33.
|
|
Fixes #3257.
|
|
Fixes #3091.
|
|
Fixes #1606.
|
|
|
|
Previous implementation was querying Fontconfig using `charset` in a pattern,
which was leading to unpredictable fallbacks in some cases, since Fontconfig
was picking the font with the most coverage for a given charset, regardless of
user configuration. Moreover all fallback was based on font_match which is
extremely slow for such performance sensitive task as a fallback, so alacritty
had a hard times on vtebench's unicode-random-write.
The new approach is to use some internal fallback list from font_sort
and iterate over it to get a proper fallback font, since it matches the
following example query from `fc-match`:
`fc-match -s "monospace:pixelsize=X:style=Y"
That being said it's more intuitive for users to setup their system Fontconfig
fallback, and also most applications are doing similar things. Moreover the new
implementation uses internal caches over Fontconfig API when possible and
performs font matches only once during load of requested font with font_sort,
which leads to dramatically improved performance on already mentioned
vtebench's unicode-random-write.
Fixes #3176.
Fixes #3134.
Fixes #2657.
Fixes #1560.
Fixes #965.
Fixes #511.
|
|
This cleans up the Alacritty scripts a bit by removing some of them
which are not recommended to be used anymore and switching from the
official FlameGraph tool to the more specialized Rust FlameGraph
implementation.
|
|
|
|
|
|
Fixes #2983.
|
|
|
|
We currently log whenever we fall back to the default config because of
an error in the config itself. We also log when the config was
successfully loaded and where it was loaded from. The only scenario
where no config related message is logged is when there is no
configuration file present.
Logging this case should make it easier to debug issues like #3240,
without requiring any knowledge from maintainers about this edgecase.
|
|
Fixes #3235.
|
|
Fixes #3238.
|
|
Fixes #3233.
|
|
Since the expansion of the selection was done after clamping it to the
grid, the selection would incorrectly move the clamped start over by one
cell when the start was to the right of the original column. By
resetting the side of the start point to `Left` before expanding, this
can be circumvented.
This also resolves a regression which broke backwards bracket selection.
Fixes #3223.
|
|
Since the assumption is usually that bold text is drawn in bright
colors, this might break some applications. However some other terminals
have already taken this leap, which should lessen the impact for
Alacritty.
Since this might still be desired and necessary for certain
applications, the config option is just switched to draw with normal
colors by default, however the old behavior can still be restored.
Fixes #2779.
|
|
Fixes: #1873
|
|
|
|
|
|
Fixes #2651.
|
|
Clippy[1] says that `.next()` is more readable than `.nth(0)`.
[1]: https://rust-lang.github.io/rust-clippy/master/index.html#iter_nth_zero
|
|
Fix reset CLI parameters on config reload
Fixes #3197.
|
|
|
|
|
|
Fixes #3198.
|
|
Fixes #3109.
|
|
This change includes dynamic escape buffer support in VTE, which allows
us to have arbitrary escape sizes.
Since tmux could potentially use very long escapes for the clipboard
escape, this allows copying more text.
Fixes #1002.
|
|
|
|
Fixes #3183.
|
|
This fixes various outdated links pointing to the old jwilm/alacritty
repository.
Since `copypasta` now has its own github repository at
https://github.com/alacritty/copypasta, the sources have been removed
from Alacritty.
|
|
Fixes #3165.
|
|
Fixes #3152.
|
|
This resolves the issue with full width glyphs getting rendered in the
last column. Since they need at least two glyphs, it is not possible to
properly render them in the last column.
Instead of rendering half of the glyph in the last column, with the
other half cut off, an additional spacer is now inserted before the wide
glyph. This means that the specific glyph in question is then three
cells wide.
Fixes #2385.
|
|
|
|
|
|
Fixes #3160.
|
|
|
|
Fixes #3154.
|
|
|
|
Fixes #2534.
|
|
Fixes #3070.
Fixes #2893.
Fixes #2877.
Fixes #2829.
Fixes #2767.
Fixes #2271.
|
|
|
|
Fixes #2226.
|
|
|
|
Fixes #3136.
|
|
Removes widestring and dunce dependencies, reduces some code duplication
and corrects a few typos.
|