| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Keeping the license as part of every file bloats up the files
unnecessarily and introduces an additional overhead to the creation of
new modules.
Since cargo already provides excellent dependency management, most of
the code-reuse of Alacritty should occur through Rust's dependency
management instead of copying it source.
If code is copied partially, copying the license from the main license
file should be just as easy as copying from the top of the file and
making some adjustments based on where it is used is likely necessary
anyways.
|
| |
|
|
|
| |
Fixes #3767.
|
|
|
|
|
|
|
|
|
|
|
| |
This commit aims to clear up the separation between Term and Grid to
make way for implementing search.
The `cursor` and `cursor_save` have been moved to the grid, since
they're always bound to their specific grid and this makes updating
easier.
Since the selection is independent of the active grid, it has been moved
to the `Term`.
|
|
|
|
|
| |
The env logger has been broken for over a year and is not used by anyone
as far as I know. This removes this option entirely in favor of
Alacritty's built-in logger level selection flags.
|
| |
|
| |
|
|
|
|
|
| |
This resolves an issue with the ScrollToBottom motion in vi mode where
it would jump between the first unoccupied cell across wrapped lines and the
first unoccupied cell in the current line.
|
|
|
| |
Fixes #1864.
|
| |
|
|
|
| |
Fixes #2761.
|
| |
|
|
|
|
|
|
|
|
|
| |
Instead of blocking on vsync, Alacritty now requests a notification from
wayland about when the next frame should be rendered. this helps with
input latency, since it gives alacritty more time to process events
before a redraw. it also prevents alacritty from drawing unless the
compositor tells it to do so.
Fixes #2851.
|
|
|
| |
Fixes: #2861.
|
|
|
|
|
|
|
|
|
|
| |
On X11 `swap_buffers` does not block for vsync. However the next OpenGl command
will block to synchronize (this is `glClear` in Alacritty), which causes a
permanent one frame delay.
Calling `glFinish` after swapping buffers forces Alacritty to finish the buffer
swap before returning control to the event loop.
Fixes #3061.
|
| |
|
| |
|
| |
|
|
|
| |
Fixes #3526.
|
| |
|
|
|
|
|
|
|
|
|
| |
This commit fixes some issues introduced by
1a8cd172e520e493bacc9c6a2ae6f80de086eaa3:
1. Vi cursor not moving properly on double/triple click
2. URL not launching via mouse click in vi mode + mouse mode
3. Ability to select in mouse mode with double/triple click regardless
of shift modifier
|
|
|
| |
Fixes #2092.
|
| |
|
|
|
| |
Fixes #3144.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This implements a basic mode for navigating inside of Alacritty's
history with keyboard bindings. They're bound by default to vi's motion
shortcuts but are fully customizable. Since this relies on key bindings
only single key bindings are currently supported (so no `ge`, or
repetition).
Other than navigating the history and moving the viewport, this mode
should enable making use of all available selection modes to copy
content to the clipboard and launch URLs below the cursor.
This also changes the rendering of the block cursor at the side of
selections, since previously it could be inverted to be completely
invisible. Since that would have caused some troubles with this keyboard
selection mode, the block cursor now is no longer inverted when it is at
the edges of a selection.
Fixes #262.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This enables live config reload for the window title. This includes
updating the title after it has been pushed and popped from the title
stack.
The dynamic title option also isn't disabled automatically anymore when
the title is set in the config. If the title is set from CLI, the
behavior is unchanged and dynamic title changes are still disabled.
If the dynamic title is disabled in the config, the title is still
updated when the config title is changed. Dynamic title now only
prevents changes to the UI's title.
|
|
|
|
|
| |
Since there were some problems with clippy suggesting changes that were
not yet available in the oldest supported Rust compiler of Alacritty,
the clippy stage has been moved from stable to 1.37.0.
|
|
|
|
|
|
|
|
| |
Fixes #3266.
Fixes #3248.
Fixes #3188.
Fixes #3177.
Fixes #2445.
Fixes #1574.
|
|
|
|
|
| |
This resolves an issue with the selection clamping, where no selection
would be rendered at all when the start was above the viewport while the
end was below it.
|
|
|
| |
Fixes #3377.
|
|
|
|
|
|
|
| |
This completely removes the tabspaces option from the Alacritty
configuration, due to frequent misuse of it. Based on some research,
none of the terminal emulators support setting the value for tabspaces
or read the terminfo to determine init_tabs value at startup. The tested
terminal emulators were URxvt, XTerm, and Termite.
|
|
|
|
| |
Since winit now filters out clicks on unfocused windows on macOS
anyways, we don't need to implement this logic ourselves anymore.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 7f4dce2ee04859fb0b48f15cf808b60065778703.
Originally it was assumed that macOS always sends the \x7f on backspace
anyways, however this is not true. It seems like the character on
backspace can change even within the same terminal session, so we need
to have our own binding to reliably set the correct binding.
A solution for #1606 should be implemented in cooperation with winit.
|
|
|
|
|
|
|
| |
Fixes #3191.
Fixes #3150.
Fixes #1465.
Fixes #1359.
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of trying to expand the start and end of a selection across
full-width glyphs, the selection should now only go from its origin to
the end without any kind of expansion.
Instead, the expansion is now done where the cells are actually checked
for their selection status, expanding across the entire full-width glyph
whenever any part of it is selected.
Fixes #3106.
|
| |
|
|
|
|
|
|
| |
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 #1606.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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: #1873
|