| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | |
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| | |
Resolves #81.
|
| | |
| |
| |
| | |
Should solve the `monospace` issue people are seeing for now.
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Fix compilation on ARM/AARCH64
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This fixes an issue where encountering some signals panicked the event
loop thread.
Resolves #76
|
| | | |
|
| |/ |
|
| |
|
|
| |
cc #53
|
| |
|
|
| |
Resolves #46.
|
| |
|
|
|
|
|
| |
This improves the situation where the user has not installed the default
configuration file.
Resolves #42.
|
| |
|
|
| |
Resolves #43.
|
| |
|
|
| |
Resolves #37.
|
| |
|
|
| |
Resolves #35.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This work started because we wanted to be able to simply say "monospace"
on Linux and have it give us some sort of font. The config format for
fonts changed to accomodate this new paradigm. As a result, italic and
bold can have different families from the normal (roman) face.
The fontconfig based font resolution probably works a lot better than
the CoreText version at this point. With CoreText, we simply iterate
over fonts and check it they match the requested properties. What's
worse is that the CoreText version requires a valid family. With
fontconfig, it will just provide the closest matching thing and use it
(unless a specific style is requested).
|
| |
|
|
| |
Shader initialization errors at startup should print a nice message now.
|
| |
|
|
|
|
| |
Previously, these could have crashed alacritty. Now, they simply print
an error message in Red to stderr. The Red format wrapper was moved to a
central location where both main.rs and the alacritty lib can access it.
|
| |
|
|
|
| |
According to:
http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-Mouse-Tracking
|
| |
|
|
| |
Resolves #22.
|
| |
|
|
|
| |
This allows consumers of the font crate to handle errors instead of the
library panicking.
|
| |
|
|
| |
Also adds a benchmark for cell.reset().
|
| |
|
|
| |
Just a bit of cleanup.
|
| |
|
|
|
|
|
|
|
|
|
| |
There was a lot of complexity around the threadsafe `Flag` type and
waking up the event loop. The idea was to prevent unnecessary calls to
the glutin window's wakeup_event_loop() method which can be expensive.
This complexity made it difficult to get synchronization between the pty
reader and the render thread correct. Now, the `dirty` flag on the
terminal is also used to prevent spurious wakeups. It is only changed
when the mutex is held, so race conditions associated with that flag
shouldn't happen.
|
| |
|
|
| |
Moving the window on macOS would cause a panic in certain circumstances.
|
| |
|
|
|
|
| |
Using underscores because it's easy. It's also wrong.
cc #11
|
| |
|
|
|
|
|
|
| |
The terminal mutex is no longer released between event processing and
doing a draw. This may fix the race condition with data arriving but not
being displayed until a subsequent event.
cc #29
|
| | |
|
| |
|
|
|
|
| |
Long lines were previously broken at the terminal width. Now, a wrapping
marker is kept on the final cell so that extra newlines are not
inserted.
|
| | |
|
| |
|
|
| |
The reloaded config was not used immediately.
|
| |
|
|
| |
Still need automatic loading into selection copy buffer for linux.
|
| |
|
|
|
|
|
|
|
|
| |
The somewhat redundant KeyBinding and MouseBinding types were removed in
favor of a Binding<T> type. This allows all binding code to be reused
for both scenarios.
The binding tests were fixed by only asserting on `is_triggered_by()`
instead of checking that the action escape sequence was delivered
properly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The event handling code grew organically over time, and with that came a
number of warts. The primary issue was with passing some random
selection of arguments to the input::Processor based on what the input
was. There was the issue that if multiple events were drained from a
single PollEventsIterator, the terminal mutex was potentially locked and
unlocked many times. Finally, and perhaps most importantly, there was no
good way to pass necessary state to the Action executor without going
through several API layers.
To fix all that, the input::ActionContext and input::Processor are now
generated once per call to the event::Processor. The input::Processor
holds onto the ActionContext so that it doesn't need to be passed
through layers of function calls. When a binding is activated, the
ActionContext is simply passed to the handler.
This did have the effect of breaking the input::Processor tests
(specifically, those relating to bindings). The issue was not addressed
in this commit since a larger refactor of the bindings is planned which
should also improve testability.
|
| |
|
|
|
|
|
| |
Various functions take some permutation of the current selection, the
terminal, and a notifier. Instead of having to juggle some number of
arguments everywhere, the `ActionContext` is constructed and then passed
around.
|
| |
|
|
|
|
| |
This adds the ability to click and drag with the mouse and have the
effect of visually selecting text. The ability to copy the selection
into a clipboard buffer is not yet implemented.
|
| |
|
|
|
| |
The main refactor broke config reloading; specifically, colors were not
updating for subsequent draws.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
All of the changes in this commit are due to clippy lints.
|
| |
|
|
| |
Resolves #25
|
| |
|
|
|
|
|
| |
This adds a trait OnResize and a separate method handle_resize to the
display. Instead of having a callback to receive resize events, a list
of &mut OnResize are passed to this new method. Doing this allowed the
only RefCell usage in the codebase to be removed :).
|
| | |
|
| |
|
|
|
|
|
| |
The cell under the cursor is now tracked in the input processor at
`self.mouse.line` and `self.mouse.column`. This could probably be
optimized to only compute the cell when in certain states, but the
calculation is cheap.
|
