summaryrefslogtreecommitdiff
path: root/src/term.c
Commit message (Collapse)AuthorAgeFilesLines
* patch 8.2.0320: no Haiku supportv8.2.0320Bram Moolenaar2020-02-261-0/+5
| | | | | Problem: No Haiku support. Solution: Add support for Haiku. (Emir Sari, closes #5605)
* patch 8.2.0302: setting 'term' may cause error in TermChanged autocommandv8.2.0302Bram Moolenaar2020-02-221-5/+8
| | | | | | Problem: Setting 'term' may cause error in TermChanged autocommand. Solution: Use aucmd_prepbuf() to switch to the buffer where the autocommand is to be executed. (closes #5682)
* patch 8.2.0260: several lines of code are duplicatedv8.2.0260Bram Moolenaar2020-02-151-0/+31
| | | | | | Problem: Several lines of code are duplicated. Solution: Move duplicated code to a function. (Yegappan Lakshmanan, closes #5330)
* patch 8.2.0231: silent system command may clear the screenv8.2.0231Bram Moolenaar2020-02-081-2/+2
| | | | | Problem: Silent system command may clear the screen. Solution: Do not clear the screen in t_te.
* patch 8.2.0156: various typos in source files and testsv8.2.0156Bram Moolenaar2020-01-261-1/+1
| | | | | Problem: Various typos in source files and tests. Solution: Fix the typos. (Emir Sari, closes #5532)
* patch 8.2.0148: mapping related function in wrong source filev8.2.0148Bram Moolenaar2020-01-241-75/+0
| | | | | | Problem: Mapping related function in wrong source file. Solution: Move the function. Add a few more test cases. (Yegappan Lakshmanan, closes #5528)
* patch 8.2.0056: execution stack is incomplete and inefficientv8.2.0056Bram Moolenaar2019-12-291-1/+1
| | | | | | Problem: Execution stack is incomplete and inefficient. Solution: Introduce a proper execution stack and use it instead of sourcing_name/sourcing_lnum. Create a string only when used.
* patch 8.1.2406: leaking memory in test_paste and test_registersv8.1.2406Bram Moolenaar2019-12-071-0/+2
| | | | | Problem: Leaking memory in test_paste and test_registers. Solution: Free the old title. Don't copy expr_line.
* patch 8.1.2395: using old C style commentsv8.1.2395Bram Moolenaar2019-12-051-523/+520
| | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate.
* patch 8.1.2350: other text for CTRL-V in Insert mode with modifyOtherKeysv8.1.2350Bram Moolenaar2019-11-261-1/+1
| | | | | | | Problem: Other text for CTRL-V in Insert mode with modifyOtherKeys. Solution: Convert the Escape sequence back to key as if modifyOtherKeys is not set, and use CTRL-SHIFT-V to get the Escape sequence itself. (closes #5254)
* patch 8.1.2331: the option.c file is still very bigv8.1.2331Bram Moolenaar2019-11-211-0/+34
| | | | | | Problem: The option.c file is still very big. Solution: Move a few functions to where they fit better. (Yegappan Lakshmanan, closes #4895)
* patch 8.1.2313: debugging where a delay comes from is not easyv8.1.2313Bram Moolenaar2019-11-171-2/+2
| | | | | Problem: Debugging where a delay comes from is not easy. Solution: Use different values when calling ui_delay().
* patch 8.1.2209: LF in escape codes may be expanded to CR-LFv8.1.2209Bram Moolenaar2019-10-241-17/+10
| | | | | Problem: LF in escape codes may be expanded to CR-LF. Solution: Do not expand LF in escape codes to CR-LF. (closes #5107)
* patch 8.1.2194: modifyOtherKeys is not enabled by defaultv8.1.2194Bram Moolenaar2019-10-201-0/+2
| | | | | Problem: ModifyOtherKeys is not enabled by default. Solution: Add t_TI and t_TE to the builtin xterm termcap.
* patch 8.1.2174: screen not recognized as supporting "sgr" mouse codesv8.1.2174Bram Moolenaar2019-10-181-4/+12
| | | | | Problem: Screen not recognized as supporting "sgr" mouse codes. Solution: Recognize screen 4.7. (Jordan Christiansen, closes #5042)
* patch 8.1.2171: mouse support not always availablev8.1.2171Bram Moolenaar2019-10-171-36/+21
| | | | | | Problem: Mouse support not always available. Solution: Enable mouse support also in tiny version. Do not define FEAT_MOUSE_XTERM on MS-Windows (didn't really work).
* patch 8.1.2170: cannot build without the +termresponse featurev8.1.2170Bram Moolenaar2019-10-171-0/+2
| | | | | Problem: Cannot build without the +termresponse feature. Solution: Add #ifdef.
* patch 8.1.2169: terminal flags are never resetv8.1.2169Bram Moolenaar2019-10-171-0/+2
| | | | | Problem: Terminal flags are never reset. Solution: Reset the flags when setting 'term'.
* patch 8.1.2145: cannot map <C-H> when modifyOtherKeys is enabledv8.1.2145Bram Moolenaar2019-10-131-13/+32
| | | | | | Problem: Cannot map <C-H> when modifyOtherKeys is enabled. Solution: Add the <C-H> mapping twice, both with modifier and as 0x08. Use only the first one when modifyOtherKeys has been detected.
* patch 8.1.2144: side effects when using t_ti to enable modifyOtherKeysv8.1.2144Bram Moolenaar2019-10-121-0/+3
| | | | | Problem: Side effects when using t_ti to enable modifyOtherKeys. Solution: Add t_TI and t_TE.
* patch 8.1.2142: some key mappings do not work with modifyOtherKeysv8.1.2142Bram Moolenaar2019-10-121-1/+10
| | | | | Problem: Some key mappings do not work with modifyOtherKeys. Solution: Remove the Shift modifier if it is already included in the key.
* patch 8.1.2134: modifier keys are not always recognizedv8.1.2134Bram Moolenaar2019-10-101-63/+126
| | | | | | 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.2123: parsing CSI sequence is messyv8.1.2123Bram Moolenaar2019-10-081-145/+158
| | | | | Problem: Parsing CSI sequence is messy. Solution: Generalize parsing a CSI sequence.
* patch 8.1.2070: mouse code is spread outv8.1.2070Bram Moolenaar2019-09-231-724/+43
| | | | | | Problem: Mouse code is spread out. Solution: Move mouse terminal code parsing to mouse.c. (Yegappan Lakshmanan, closes #4966)
* patch 8.1.2062: the mouse code is spread outv8.1.2062Bram Moolenaar2019-09-211-223/+10
| | | | | | Problem: The mouse code is spread out. Solution: Move all the mouse code to mouse.c. (Yegappan Lakshmanan, closes #4959)
* patch 8.1.1901: the +insert_expand feature is not always availablev8.1.1901Bram Moolenaar2019-08-211-2/+0
| | | | | Problem: The +insert_expand feature is not always available. Solution: Graduate the +insert_expand feature.
* patch 8.1.1891: functions used in one file are globalv8.1.1891Bram Moolenaar2019-08-201-3/+5
| | | | | Problem: Functions used in one file are global. Solution: Add "static". (Yegappan Lakshmanan, closes #4840)
* patch 8.1.1887: the +cmdline_compl feature is not in the tiny versionv8.1.1887Bram Moolenaar2019-08-181-4/+0
| | | | | Problem: The +cmdline_compl feature is not in the tiny version. Solution: Graduate the +cmdline_compl feature.
* patch 8.1.1739: deleted match highlighting not updated in other windowv8.1.1739Bram Moolenaar2019-07-241-0/+1
| | | | | | Problem: Deleted match highlighting not updated in other window. Solution: Mark the window for refresh. (closes #4720) Also fix that ambi-width check clears with wrong attributes.
* patch 8.1.1664: GUI resize may cause changing Rows at a bad timev8.1.1664Bram Moolenaar2019-07-121-1/+5
| | | | | | Problem: GUI resize may cause changing Rows at a bad time. (Dominique Pelle) Solution: Postpone resizing while updating the screen.
* patch 8.1.1481: length for two-digit rgb termresponse is off by onev8.1.1481Bram Moolenaar2019-06-061-1/+1
| | | | | Problem: Length for two-digit rgb termresponse is off by one. Solution: Adjust the length. (closes #4494)
* patch 8.1.1471: 'background' not correctly set for 2-digit rgb termresponsev8.1.1471Bram Moolenaar2019-06-051-7/+10
| | | | | Problem: 'background' not correctly set for 2-digit rgb termresponse. Solution: Adjust what digit to use. (closes #4495)
* patch 8.1.1469: no test for checking the cursor style responsev8.1.1469Bram Moolenaar2019-06-051-24/+25
| | | | | Problem: No test for checking the cursor style response. Solution: Add a simple test. Also include the missing part of 8.1.1464.
* patch 8.1.1464: only 4-digit rgb termresponse is recognizedv8.1.1464Bram Moolenaar2019-06-041-5/+11
| | | | | Problem: Only 4-digit rgb termresponse is recognized. Solution: Also recognize 2-digit rgb response. (closes #4486)
* patch 8.1.1414: alloc() returning "char_u *" causes a lot of type castsv8.1.1414Bram Moolenaar2019-05-281-5/+3
| | | | | | Problem: Alloc() returning "char_u *" causes a lot of type casts. Solution: Have it return "void *". (Mike Williams) Define ALLOC_ONE() to check the simple allocations.
* patch 8.1.1393: unnecessary type castsv8.1.1393Bram Moolenaar2019-05-251-2/+2
| | | | | Problem: Unnecessary type casts. Solution: Remove type casts from alloc() and lalloc() calls. (Mike Williams)
* patch 8.1.1384: using "int" for alloc() often results in compiler warningsv8.1.1384Bram Moolenaar2019-05-241-2/+2
| | | | | | Problem: Using "int" for alloc() often results in compiler warnings. Solution: Use "size_t" and remove type casts. Remove alloc_check(), Vim only works with 32 bit ints anyway.
* patch 8.1.1323: 'mouse' option is reset when using GPM mousev8.1.1323Bram Moolenaar2019-05-111-2/+13
| | | | | Problem: 'mouse' option is reset when using GPM mouse. Solution: Add flag for GPM mouse.
* patch 8.1.1315: there is always a delay if a termrequest is never answeredv8.1.1315Bram Moolenaar2019-05-101-90/+132
| | | | | | Problem: There is always a delay if a termrequest is never answered. Solution: When the response is not received within two seconds consider the request to have failed.
* patch 8.1.1296: crash when using invalid command line argumentv8.1.1296Bram Moolenaar2019-05-081-4/+4
| | | | | Problem: Crash when using invalid command line argument. Solution: Check for options not being initialized.
* patch 8.1.1265: when GPM mouse support is enabled double clicks do not workv8.1.1265Bram Moolenaar2019-05-041-17/+24
| | | | | | Problem: When GPM mouse support is enabled double clicks in xterm do not work. Solution: Use KS_GPM_MOUSE for GPM mouse events.
* patch 8.1.1254: mapping completion contains dead codev8.1.1254Bram Moolenaar2019-05-031-18/+0
| | | | | Problem: Mapping completion contains dead code. Solution: Remove the code.
* patch 8.1.1251: no test for completion of mapping keysv8.1.1251Bram Moolenaar2019-05-031-11/+9
| | | | | Problem: No test for completion of mapping keys. Solution: Add a test. Also clean up the code.
* patch 8.1.1246: cannot handle negative mouse coordinate from urxvtv8.1.1246Bram Moolenaar2019-05-021-3/+4
| | | | | | Problem: Cannot handle negative mouse coordinate from urxvt. Solution: Accept '-' where a digit is expected. (Vincent Vinel, closes #4326)
* patch 8.1.1230: a lot of code is shared between vim.exe and gvim.exev8.1.1230Bram Moolenaar2019-04-281-11/+34
| | | | | | Problem: A lot of code is shared between vim.exe and gvim.exe. Solution: Optionally put the shared code in vim.dll. (Ken Takata, closes #4287)
* patch 8.1.1198: bracketed paste may remain active after Vim existsv8.1.1198Bram Moolenaar2019-04-211-7/+11
| | | | | | | Problem: Bracketed paste may remain active after Vim exists, because the terminal emulater restores the setting. Solution: Set/reset bracketed paste mode before setting the terminal mode. (closes #3579)
* patch 8.1.1194: typos and small problems in source filesv8.1.1194Bram Moolenaar2019-04-211-1/+1
| | | | | Problem: Typos and small problems in source files. Solution: Small fixes.
* patch 8.1.1127: getwinpos() doesn't work in terminal on MS-Windows consolev8.1.1127Bram Moolenaar2019-04-061-8/+8
| | | | | Problem: getwinpos() doesn't work in terminal on MS-Windows console. Solution: Adjust #ifdefs. Disable test for MS-Windows console.
* patch 8.1.1105: long escape sequences may be split upv8.1.1105Bram Moolenaar2019-04-031-7/+15
| | | | | | Problem: Long escape sequences may be split up. Solution: Assume esccape sequences can be up to 80 bytes long. (Nobuhiro Takasaki, closes #4196)
* patch 8.1.1096: MS-Windows: cannot distinguish BS and CTRL-Hv8.1.1096Bram Moolenaar2019-03-301-0/+1
| | | | | Problem: MS-Windows: cannot distinguish BS and CTRL-H. Solution: Add code for VK_BACK. (Linwei, closes #1833)