summaryrefslogtreecommitdiff
path: root/src/libvterm
Commit message (Collapse)AuthorAgeFilesLines
* patch 8.2.2487: terminal shows garbage after double-wide characterv8.2.2487Bram Moolenaar2021-02-081-1/+2
| | | | | | | 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)
* patch 8.2.2086: libvterm tests are only run on Linuxv8.2.2086Bram Moolenaar2020-12-032-3/+2
| | | | | Problem: Libvterm tests are only run on Linux. Solution: Use static libraries. (Ozaki Kiichi, closes #7419)
* patch 8.2.1547: various comment problemsv8.2.1547Bram Moolenaar2020-08-301-2/+5
| | | | | Problem: Various comment problems. Solution: Update comments.
* patch 8.2.1424: Mac build failsv8.2.1424Bram Moolenaar2020-08-111-2/+2
| | | | | | Problem: Mac build fails. Solution: Adjust configure to not fall back to Athena. Adjust some other files.
* patch 8.2.1353: crash when drawing double-wide character in terminal windowv8.2.1353Bram Moolenaar2020-08-021-1/+6
| | | | | | Problem: Crash when drawing double-wide character in terminal window. (Masato Nishihata) Solution: Check getcell() returning NULL. (issue #6141)
* patch 8.2.1108: mouse left-right scroll is not supported in terminal windowv8.2.1108Bram Moolenaar2020-07-011-2/+2
| | | | | Problem: Mouse left-right scroll is not supported in terminal window. Solution: Implement mouse codes 6 and 7. (Trygve Aaberge, closes #6363)
* patch 8.2.1094: dead code in libvtermv8.2.1094Bram Moolenaar2020-06-291-2/+1
| | | | | Problem: Dead code in libvterm. Solution: Remove condition that is always true.
* patch 8.2.1072: missing libvterm testv8.2.1072Bram Moolenaar2020-06-272-4/+20
| | | | | Problem: Missing libvterm test. Solution: Sync with libvterm revision 768.
* patch 8.2.1030: reducing size of a terminal window may cause a crashv8.2.1030Bram Moolenaar2020-06-212-10/+16
| | | | | Problem: Reducing size of a terminal window may cause a crash. Solution: Make sure the row and column don't become negative. (closes #6273)
* patch 8.2.1010: build failure in libvterm with debug enabledv8.2.1010Bram Moolenaar2020-06-191-1/+1
| | | | | Problem: Build failure in libvterm with debug enabled. (John Little) Solution: Use "->" instead of ".".
* patch 8.2.0989: crash after resizing a terminal windowv8.2.0989Bram Moolenaar2020-06-162-0/+17
| | | | | Problem: Crash after resizing a terminal window. (August Masquelier) Solution: Add check for valid row in libvterm. (closes #6273)
* patch 8.2.0831: compiler warnings for integer sizesv8.2.0831Bram Moolenaar2020-05-271-2/+2
| | | | | Problem: Compiler warnings for integer sizes. Solution: Add type casts. (Mike Williams)
* patch 8.2.0813: libvterm code is slightly different from upstreamv8.2.0813Bram Moolenaar2020-05-2213-164/+168
| | | | | | Problem: libvterm code is slightly different from upstream. Solution: Use upstream text to avoid future merge problems. Mainly comment style changes.
* patch 8.2.0804: libvterm code lags behind the upstream versionv8.2.0804Bram Moolenaar2020-05-219-152/+324
| | | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revision 727, but add the index instead of switching between RGB and indexed.
* patch 8.2.0803: libvterm code lags behind the upstream versionv8.2.0803Bram Moolenaar2020-05-206-29/+44
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 764 - 767
* patch 8.2.0802: libvterm code lags behind the upstream versionv8.2.0802Bram Moolenaar2020-05-209-11/+85
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 759 - 762.
* patch 8.2.0799: build fails if snprintf is not availablev8.2.0799Bram Moolenaar2020-05-191-3/+3
| | | | | Problem: Build fails if snprintf is not available. Solution: Use vim_snprintf().
* patch 8.2.0798: libvterm code lags behind the upstream versionv8.2.0798Bram Moolenaar2020-05-1912-301/+369
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 755 - 758.
* patch 8.2.0797: MS-Windows: compiler still can't handle C99 constructv8.2.0797Bram Moolenaar2020-05-191-2/+1
| | | | | Problem: MS-Windows: compiler still can't handle C99 construct. Solution: Change to C90 construct. (Dominique Pelle, closes #6106)
* patch 8.2.0796: MS-Windows: compiler can't handle C99 construct in libvtermv8.2.0796Bram Moolenaar2020-05-181-3/+3
| | | | | Problem: MS-Windows: compiler can't handle C99 construct in libvterm. Solution: Change to C90 construct.
* patch 8.2.0795: libvterm code lags behind the upstream versionv8.2.0795Bram Moolenaar2020-05-189-75/+151
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 748 - 754.
* patch 8.2.0794: libvterm code lags behind the upstream versionv8.2.0794Bram Moolenaar2020-05-186-44/+85
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 743 - 747.
* patch 8.2.0788: memory leak in libvtermv8.2.0788Bram Moolenaar2020-05-171-0/+8
| | | | | Problem: Memory leak in libvterm. Solution: free tmpbuffer.
* patch 8.2.0787: libvterm code lags behind the upstream versionv8.2.0787Bram Moolenaar2020-05-171-138/+163
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 741 - 742.
* patch 8.2.0785: libvterm code lags behind the upstream versionv8.2.0785Bram Moolenaar2020-05-178-13/+95
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 734 - 740.
* patch 8.2.0784: libvterm code lags behind the upstream versionv8.2.0784Bram Moolenaar2020-05-175-43/+82
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 730 - 733.
* patch 8.2.0783: libvterm code lags behind the upstream versionv8.2.0783Bram Moolenaar2020-05-176-52/+62
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 728 - 729.
* patch 8.2.0780: libvterm code lags behind the upstream versionv8.2.0780Bram Moolenaar2020-05-1712-0/+1
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 724 - 726.
* patch 8.2.0778: libvterm code lags behind the upstream versionv8.2.0778Bram Moolenaar2020-05-175-3/+159
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revisions 720 - 723.
* patch 8.2.0776: libvterm code lags behind the upstream versionv8.2.0776Bram Moolenaar2020-05-175-0/+151
| | | | | Problem: Libvterm code lags behind the upstream version. Solution: Include revision 719.
* patch 8.2.0553: error for unused argumentv8.2.0553Bram Moolenaar2020-04-121-1/+1
| | | | | Problem: Error for unused argument. Solution: Add UNUSED.
* patch 8.2.0550: some changes in the libvterm upstream codev8.2.0550Bram Moolenaar2020-04-121-14/+19
| | | | | Problem: Some changes in the libvterm upstream code. Solution: Include some changes.
* patch 8.2.0545: unused arguments ignored in non-standard wayv8.2.0545Bram Moolenaar2020-04-111-36/+18
| | | | | Problem: Unused arguments ignored in non-standard way. Solution: Add UNUSED instead of (void).
* patch 8.2.0541: Travis CI does not give compiler warningsv8.2.0541Bram Moolenaar2020-04-111-5/+25
| | | | | | Problem: Travis CI does not give compiler warnings. Solution: Add flags for warnings. Fix uncovered problems. (Ozaki Kiichi, closes #5898)
* patch 8.2.0156: various typos in source files and testsv8.2.0156Bram Moolenaar2020-01-262-2/+2
| | | | | Problem: Various typos in source files and tests. Solution: Fix the typos. (Emir Sari, closes #5532)
* patch 8.2.0106: printf formats are not exactly rightv8.2.0106Bram Moolenaar2020-01-082-2/+2
| | | | | Problem: Printf formats are not exactly right. Solution: Adjust signed/unsigned conversions. (Frazer Clews, closes #5456)
* patch 8.1.2389: using old C style commentsv8.1.2389Bram Moolenaar2019-12-045-52/+52
| | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate.
* patch 8.1.2374: unused parts of libvterm are includedv8.1.2374Bram Moolenaar2019-12-013-886/+0
| | | | | Problem: Unused parts of libvterm are included. Solution: Delete the unused files.
* patch 8.1.2134: modifier keys are not always recognizedv8.1.2134Bram Moolenaar2019-10-104-0/+18
| | | | | | Problem: Modifier keys are not always recognized. Solution: Handle key codes generated by xterm with modifyOtherKeys set. Add this to libvterm so we can debug it.
* patch 8.1.2128: renamed libvterm sources makes merging difficultv8.1.2128Bram Moolenaar2019-10-102-0/+0
| | | | | | | Problem: Renamed libvterm sources makes merging difficult. Solution: Rename back to the original name and only rename the .o files. Also clean the libvterm build artifacts. (James McCoy, closes #5027)
* patch 8.1.2076: crash when trying to put a terminal in a popup windowv8.1.2076Bram Moolenaar2019-09-251-0/+2
| | | | | | Problem: Crash when trying to put a terminal buffer in a popup window. Solution: Check for NULL buffer. Do not allow putting a terminal in a popup window.
* patch 8.1.2062: the mouse code is spread outv8.1.2062Bram Moolenaar2019-09-211-0/+0
| | | | | | Problem: The mouse code is spread out. Solution: Move all the mouse code to mouse.c. (Yegappan Lakshmanan, closes #4959)
* patch 8.1.2027: MS-Windows: problem with ambiwidth charactersv8.1.2027Bram Moolenaar2019-09-135-8/+100
| | | | | | Problem: MS-Windows: problem with ambiwidth characters. Solution: handle ambiguous width characters in ConPTY on Windows 10 (1903). (Nobuhiro Takasaki, closes #4411)
* patch 8.1.1885: comments in libvterm are inconsistentv8.1.1885Bram Moolenaar2019-08-1817-298/+524
| | | | | Problem: Comments in libvterm are inconsistent. Solution: Use // comments. Als update the table of combining characters.
* patch 8.1.1222: build still fails on MS-Windowsv8.1.1222Bram Moolenaar2019-04-271-1/+1
| | | | | Problem: Build still fails on MS-Windows. Solution: Move another declaration to start of block.
* patch 8.1.1220: build fails on MS-Windowsv8.1.1220Bram Moolenaar2019-04-271-1/+1
| | | | | Problem: Build fails on MS-Windows. Solution: Move declaration to start of block.
* patch 8.1.1219: not checking for NULL return from alloc()v8.1.1219Bram Moolenaar2019-04-272-0/+10
| | | | | Problem: Not checking for NULL return from alloc(). Solution: Add checks. (Martin Kunev, closes #4303, closes #4174)
* patch 8.1.1125: libvterm does not handle the window position reportv8.1.1125Bram Moolenaar2019-04-061-0/+10
| | | | | | Problem: Libvterm does not handle the window position report. Solution: Let libvterm call the fallback CSI handler when not handling CSI sequence. Handle the window position report in Vim.
* patch 8.1.1086: too many curly bracesv8.1.1086Bram Moolenaar2019-03-301-2/+3
| | | | | | Problem: Too many curly braces. Solution: Remove curly braces where they are not needed. (Hirohito Higashi, closes #3982)
* patch 8.1.0633: crash when out of memory while opening a terminal windowv8.1.0633Bram Moolenaar2018-12-243-13/+43
| | | | | Problem: Crash when out of memory while opening a terminal window. Solution: Handle out-of-memory more gracefully.