| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | refactor: adopt vterm | dundargoc | 2025-01-07 |
| | | | | | | | We have changed too much to consider it a mere bundled dependency (such as unicode handling in e3bfcf2fd4a4ebf00b104b082cfe83c8144a842d), and can consider it our own at this point. | ||
| * | fix(terminal): handle C0 characters in OSC terminator (#30090) | Gregory Anders | 2024-08-19 |
| | | | | | | | | | | | | | | | When a C0 character is present in an OSC terminator (i.e. after the ESC but before a \ (0x5c) or printable character), vterm executes the control character and resets the current string fragment. If the C0 character is the final byte in the sequence, the string fragment has a zero length. However, because the VT parser is still in the "escape" state, vterm attempts to subtract 1 from the string length (to account for the escape character). When the string fragment is empty, this causes an underflow in the unsigned size variable, resulting in a buffer overflow. The fix is simple: explicitly check if the string length is non-zero before subtracting. | ||
| * | build(deps): vendor libvterm at v0.3.3 | Christian Clason | 2024-08-10 |
| Problem: Adding support for modern Nvim features (reflow, OSC 8, full utf8/emoji support) requires coupling libvterm to Nvim internals (e.g., utf8proc). Solution: Vendor libvterm at v0.3.3. | |||
 |
index : rneovim.git | |
| Neovim fork with Rahm's personal hacks. |
| aboutsummaryrefslogtreecommitdiff |