| Age | Commit message (Collapse) | Author |
|---|
|
Problem: wrong upstream version in libvterm README
Solution: correct version to 839
related: #12746
Signed-off-by: Christian Brabandt <cb@256bit.org>
|
|
Problem: patch 1916 (fixed terminal size) not optimal
Solution: Add defines to make it easier changeable later
Signed-off-by: Christian Brabandt <cb@256bit.org>
|
|
Problem: Crash when allocating large terminal screen
Solution: Don't allow values > 1000 for terminal
screen columns and rows
closes: #13126
Signed-off-by: Christian Brabandt <cb@256bit.org>
|
|
Problem: libvterm slightly outdated
Solution: Update libvterm from rev 818 to rev 839
Notable fix: libvterm now handles DECSM/DECRM with multiple arguents,
so several ncurses programs (e.g. nnn) can enable mouse properly when
run in Vim's terminal in XTerm.
closes: #12746
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
|
|
Problem: Crash when opening a very small terminal window.
Solution: Instead of crashing fix the cursor position. (closes #11697)
|
|
Problem: Libvterm does not support the XTQMODKEYS request.
Solution: Implement the XTQMODKEYS request and response. Update the keycode
check results.
|
|
Problem: Various code formatting issues.
Solution: Improve code formatting.
|
|
Problem: Cannot debug the Kitty keyboard protocol with TermDebug.
Solution: Add Kitty keyboard protocol support to the libvterm fork.
Recognize the escape sequences that the protocol generates. Add
the 'keyprotocol' option to allow the user to specify for which
terminal what protocol is to be used, instead of hard-coding this.
Add recognizing the kitty keyboard protocol status.
|
|
Problem: libvterm with modifyOtherKeys level 2 does not match xterm.
Solution: Adjust key code escape sequences to be the same as what xterm
sends in modifyOtherKeys level 2 mode. Check the value of
no_reduce_keys before using it.
|
|
Problem: Workaround to rename "small" to "smallfont" is clumsy.
Solution: Undefine "small" after including windows.h. (Ken Takata)
|
|
Problem: MSVC can't have field name "small".
Solution: Rename small to smallfont.
|
|
Problem: The libvterm code is outdated.
Solution: Include libvterm changes from revision 802 to 817. Revert some
changes made for C89.
|
|
Problem: The libvterm code is outdated.
Solution: Include libvterm changes from revision 790 to 801.
|
|
Problem: Clang on MS-Windows produces warnings.
Solution: Avoid the warnings. (Yegappan Lakshmanan, closes #10546)
|
|
Problem: Building libvterm fails with MSVC.
Solution: Don't use C99 construct.
|
|
Problem: Libvterm is outdated.
Solution: Include patches from revision 769 to revision 789.
|
|
Problem: Looking terminal colors is a bit slow.
Solution: Cache the terminal colors. (closes #9130, closes #9058)
|
|
Problem: Terminal shows garbage after double-wide character with a
combining character. (Kyoichiro Yamada)
Solution: Libvterm: do not add the width of the combining character to the
glyph width. (closes #7801)
|
|
Problem: Libvterm tests are only run on Linux.
Solution: Use static libraries. (Ozaki Kiichi, closes #7419)
|
|
Problem: Various comment problems.
Solution: Update comments.
|
|
Problem: Mac build fails.
Solution: Adjust configure to not fall back to Athena. Adjust some other
files.
|
|
Problem: Crash when drawing double-wide character in terminal window.
(Masato Nishihata)
Solution: Check getcell() returning NULL. (issue #6141)
|
|
Problem: Mouse left-right scroll is not supported in terminal window.
Solution: Implement mouse codes 6 and 7. (Trygve Aaberge, closes #6363)
|
|
Problem: Dead code in libvterm.
Solution: Remove condition that is always true.
|
|
Problem: Missing libvterm test.
Solution: Sync with libvterm revision 768.
|
|
Problem: Reducing size of a terminal window may cause a crash.
Solution: Make sure the row and column don't become negative. (closes #6273)
|
|
Problem: Build failure in libvterm with debug enabled. (John Little)
Solution: Use "->" instead of ".".
|
|
Problem: Crash after resizing a terminal window. (August Masquelier)
Solution: Add check for valid row in libvterm. (closes #6273)
|
|
Problem: Compiler warnings for integer sizes.
Solution: Add type casts. (Mike Williams)
|
|
Problem: libvterm code is slightly different from upstream.
Solution: Use upstream text to avoid future merge problems. Mainly comment
style changes.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revision 727, but add the index instead of switching
between RGB and indexed.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 764 - 767
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 759 - 762.
|
|
Problem: Build fails if snprintf is not available.
Solution: Use vim_snprintf().
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 755 - 758.
|
|
Problem: MS-Windows: compiler still can't handle C99 construct.
Solution: Change to C90 construct. (Dominique Pelle, closes #6106)
|
|
Problem: MS-Windows: compiler can't handle C99 construct in libvterm.
Solution: Change to C90 construct.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 748 - 754.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 743 - 747.
|
|
Problem: Memory leak in libvterm.
Solution: free tmpbuffer.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 741 - 742.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 734 - 740.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 730 - 733.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 728 - 729.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 724 - 726.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 720 - 723.
|
|
Problem: Libvterm code lags behind the upstream version.
Solution: Include revision 719.
|
|
Problem: Error for unused argument.
Solution: Add UNUSED.
|
|
Problem: Some changes in the libvterm upstream code.
Solution: Include some changes.
|
|
Problem: Unused arguments ignored in non-standard way.
Solution: Add UNUSED instead of (void).
|
