| Age | Commit message (Collapse) | Author |
|---|
|
cc #93
|
|
cc #116
|
|
Better bounds checking.
|
|
- Rename wrap to input_needs_wrap and providing documentation.
- Standardize on min.
- Optimization on subtracting col.
|
|
Most of the crashes on resize were due to columns and lines being set to
zero. This causes all sorts of other checks within the code to ensure
these values are greater than zero before running calculations. To avoid
this we just need to ensure that lines and columns are some non zero
value. This is seems to be what gnome terminal does. I have selected
2 lines and two columns for min terminal size for now.
|
|
|
|
This implementation of line wrapping ensures self.cursor.col is never out
of bounds, thus not requiring checking.
|
|
- Remove the use of limit.
- Reduce the number of comparisons.
When using numbers provided by the PTY for subtractions there is a extra
step of ensuring that we won't trigger failure on testing when trying to
subtract form zero.
** NOTE **
This commit fails fails the tmux_git_log test. I am submitting a PR to
talk about the test. I think the test was generated before a few things
were fixed the final test gird still has cells that should have been
scrolled off the screen. Also, comparing output from gnome-terminal
there is no difference. So this PR is here to discuss and gather
information on balding test and discussing the possibility that this test
may be flawed.
** NOTE **
|
|
Fixes a slew of bounds issues.
|
|
Add "shell" option to config
|
|
|
|
|
|
|
|
|
|
|
|
cc #87, #55
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This allows you to configure the shell to use when alacritty starts.
cc: #122
|
|
|
|
|
|
|
|
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.
|
