| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This resolves an issue with parsing of DCS escapes, where it would try
to write parameters beyond the maximum parameter count limit.
Fixes #50.
|
| |
|
|
|
|
| |
Since ESC escapes cannot have parameters, they have been removed from
the `esc_dispatch` function.
|
|
|
|
| |
Fixes #46.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Even though the ST terminator is the only officially supported
terminator, some applications still rely on BEL to work properly. Both
have been supported historically, however there was no way for the
terminal to tell which terminator was used.
Since OSC escapes frequently offer the `?` parameter to query for the
current format, some applications expect the response terminator to
match the request terminator. To make it possible to support this, the
osc_dispatcher is now informed when the BEL terminator was used.
Since the C1 ST terminator was not yet supported for OSC escapes,
support for it has also been added.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This replaces the existing travis setup with the default for the
Alacritty organization.
This includes making it a requirement to build on 1.36.0.
|
|
|
| |
Fixes #24.
|
| |
|
|
|
|
|
| |
This renames the generate_state_changes proc macro to include the `vte_`
prefix, since it's not useful to anyone other than our `vte` crate.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This completely removes the `codegen` project, which relied on outdated
libraries to parse DSLs to build the utf8 and vte state tables, to make
the library easier to maintain.
The utf8 table could be completely removed in favor of a `match`
statement, which also lead to a performance improvement with the utf8
parser.
The vte table did not benefit from `match` statements at all and instead
had significantly worse performance with it. To replace the old
codegeneration for vte, the `generate_state_changes` crate has been
created instead, which uses the language's proc_macro feature to create
a `const fn` which will generate the table at compile time.
|
|
|
|
|
|
| |
This moves all crates in the workspace to the latest Rust standard and
resolves various style and formatting issues.
Fixes #32.
|
| |
|
|\ |
|
|/ |
|
|\
| |
| | |
Fixes #28.
|
|/ |
|
|\ |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CSI escape sequences are limited to 16 parameters using the
`MAX_PARAMS` constant.
To make sure no more params are parsed, the CSI parser stops when the
parameter index reaches `MAX_PARAMS`, however this means that it stops
at index 16, which means that the number of params would be 17 since
arrays start at 0.
To fix this off-by-one error the CSI parser now stops when the index
reaches `MAX_PARAMS - 1`, which means it will stop when the index
reaches the last element in an array with `MAX_PARAMS` number of
elements.
This fixes jwilm/alacritty#1505.
|
|
|
|
| |
osc_dispatch calls were being logged as csi_dispatch
|
|
|
|
| |
This is a purely cosmetic change at the moment.
|
| |
|
|
|
|
| |
Allows testing everything with `cargo test --all`.
|
|
|
|
| |
but https links work.
|
| |
|
| |
|
| |
|
|
|
|
| |
Links against STD to allow use of Vec.
|
| |
|
|
|
|
|
|
| |
This will allow the README to be rendered on crates.io.
Bumped version so this can be published.
|
| |
|
|
|
|
|
|
|
| |
This commit ensures that 'num_params' is never incremented beyond
MAX_PARAMS. Additionally, an extra parameter is added to the
corresponding OSC test (17 params or MAX_PARAMS + 1) to ensure that the
proper behavior is tested.
|