summaryrefslogtreecommitdiff
path: root/runtime/pack/dist/opt/termdebug
Commit message (Collapse)AuthorAgeFilesLines
* Update runtime filesBram Moolenaar2023-04-221-13/+12
|
* Update runtime filesBram Moolenaar2022-11-181-2/+9
|
* Update runtime filesBram Moolenaar2022-06-251-1/+2
|
* Update runtime filesBram Moolenaar2022-06-231-3/+3
|
* patch 8.2.5010: the terminal debugger uses various global variablesv8.2.5010Bram Moolenaar2022-05-231-35/+88
| | | | | Problem: The terminal debugger uses various global variables. Solution: Add a dictionary to hold the terminal debugger preferences.
* Update runtime files, translationsBram Moolenaar2022-05-091-3/+3
|
* Update runtime filesBram Moolenaar2022-05-071-2/+2
|
* Update runtime filesBram Moolenaar2022-04-181-27/+48
|
* Update runtime filesBram Moolenaar2022-03-191-60/+61
|
* Update runtime filesBram Moolenaar2022-01-231-1/+2
|
* Update runtime filesBram Moolenaar2022-01-161-2/+14
|
* Update runtime filesBram Moolenaar2022-01-081-5/+5
|
* Update runtime filesBram Moolenaar2021-12-241-5/+10
|
* Update runtime filesBram Moolenaar2021-12-161-11/+29
|
* Update runtime filesBram Moolenaar2021-12-051-10/+15
|
* Update runtime files.Bram Moolenaar2021-11-271-85/+116
|
* Update runtime filesBram Moolenaar2021-11-211-51/+98
|
* Update runtime filesBram Moolenaar2021-11-161-1/+3
|
* Update runtime filesBram Moolenaar2021-11-071-7/+22
|
* Update runtime filesBram Moolenaar2021-08-291-1/+5
|
* Update runtime filesBram Moolenaar2021-08-141-1/+22
|
* Update runtime filesBram Moolenaar2021-05-301-10/+36
|
* Update runtime filesBram Moolenaar2021-05-161-2/+4
|
* Update runtime files.Bram Moolenaar2021-01-111-3/+159
|
* Update runtime files.Bram Moolenaar2020-12-101-3/+7
|
* Update runtime filesBram Moolenaar2020-11-051-2/+2
|
* Update runtime files.Bram Moolenaar2020-10-261-3/+23
|
* patch 8.2.1556: cursorline highlighting always overrules sign highlightingv8.2.1556Bram Moolenaar2020-08-311-2/+2
| | | | | | Problem: Cursorline highlighting always overrules sign highlighting. Solution: Combine the highlighting, use the priority to decide how. (closes #6812)
* Update runtime files.Bram Moolenaar2020-07-261-1/+1
|
* Update runtime filesBram Moolenaar2020-06-141-2/+2
|
* Update runtime filesBram Moolenaar2020-05-261-4/+9
|
* Update runtime files.Bram Moolenaar2020-02-261-1/+1
|
* Minor runtime file updates.Bram Moolenaar2019-12-111-2/+2
|
* Update runtime files.Bram Moolenaar2019-11-301-2/+2
|
* patch 8.1.2103: wrong error message if "termdebugger" is not executablev8.1.2103Bram Moolenaar2019-09-301-3/+8
| | | | | | Problem: wrong error message if "termdebugger" is not executable. Solution: Check if "termdebugger" is executable and give a clear error message. (Ozaki Kiichi, closes #5000) Fix indents.
* Updte runtime filesBram Moolenaar2019-09-201-64/+81
|
* patch 8.1.1977: terminal debugger plugin may hangv8.1.1977Bram Moolenaar2019-09-041-7/+8
| | | | | Problem: Terminal debugger plugin may hang. Solution: Wait longer when still reading symbols.
* Runtime files update.Bram Moolenaar2019-08-311-0/+4
|
* Update runtime filesBram Moolenaar2019-07-131-2/+2
|
* Update runtime files.Bram Moolenaar2019-05-261-0/+8
|
* patch 8.1.0621: terminal debugger does not handle unexpected debugger exitv8.1.0621Bram Moolenaar2018-12-221-5/+17
| | | | | Problem: Terminal debugger does not handle unexpected debugger exit. Solution: Check for debugger job ended and close unused buffers. (Damien)
* patch 8.1.0575: Termdebug: clearing multi-breakpoint does not workv8.1.0575Bram Moolenaar2018-12-091-48/+92
| | | | | | Problem: Termdebug: clearing multi-breakpoint does not work. Solution: Delete all X.Y breakpoints. Keep more information about placed breakpoints. (Ozaki Kiichi, closes #3641)
* patch 8.1.0557: Termdebug: gdb may use X.Y for breakpoint numberv8.1.0557Bram Moolenaar2018-12-021-80/+102
| | | | | Problem: Termdebug: gdb may use X.Y for breakpoint number. Solution: Handle X.Y breakpoint numbers. (Yasuhiro Matsumoto, close #3641)
* Update runtime files.Bram Moolenaar2018-07-291-1/+1
|
* patch 8.1.0196: terminal debugger error with .gdbinit filev8.1.0196Bram Moolenaar2018-07-191-1/+2
| | | | | | Problem: Terminal debugger error with .gdbinit file. Solution: Check two lines for the "new ui" response. (hint from Hirohito Higashi)
* patch 8.1.0195: terminal debugger commands don't always workv8.1.0195Bram Moolenaar2018-07-191-0/+5
| | | | | | Problem: Terminal debugger commands don't always work. (Dominique Pelle) Solution: Set 'cpo' to its default value when defining commands. (Christian Brabandt)
* patch 8.1.0193: terminal debugger buttons don't always workv8.1.0193Bram Moolenaar2018-07-171-0/+6
| | | | | Problem: Terminal debugger buttons don't always work. (Dominique Pelle) Solution: Set 'cpo' to its default value.
* patch 8.1.0100: terminal debugger: error when setting a watch pointv8.1.0100Bram Moolenaar2018-06-231-0/+5
| | | | | Problem: Terminal debugger: error when setting a watch point. Solution: Don't try defining a sign for a watch point.
* patch 8.1.0093: non-MS-Windows: Cannot interrupt gdb when program is runningv8.1.0093Bram Moolenaar2018-06-211-5/+10
| | | | | Problem: non-MS-Windows: Cannot interrupt gdb when program is running. Solution: Only use debugbreak() on MS-Windows.
* patch 8.1.0091: MS-Windows: Cannot interrupt gdb when program is runningv8.1.0091Bram Moolenaar2018-06-201-11/+33
| | | | | | Problem: MS-Windows: Cannot interrupt gdb when program is running. Solution: Add debugbreak() and use it in the terminal debugger. Respect 'modified' in a prompt buffer.
View Lorry Controller Status