patch 8.1.0557: Termdebug: gdb may use X.Y for breakpoint number

Problem: Termdebug: gdb may use X.Y for breakpoint number.
Solution: Handle X.Y breakpoint numbers. (Yasuhiro Matsumoto, close #

patch 8.1.0557: Termdebug: gdb may use X.Y for breakpoint number

Problem: Termdebug: gdb may use X.Y for breakpoint number.
Solution: Handle X.Y breakpoint numbers. (Yasuhiro Matsumoto, close #3641)

show more ...

Update runtime files.

patch 8.1.0196: terminal debugger error with .gdbinit file

Problem: Terminal debugger error with .gdbinit file.
Solution: Check two lines for the "new ui" response. (hint from Hirohito

patch 8.1.0196: terminal debugger error with .gdbinit file

Problem: Terminal debugger error with .gdbinit file.
Solution: Check two lines for the "new ui" response. (hint from Hirohito
Higashi)

show more ...

patch 8.1.0195: terminal debugger commands don't always work

Problem: Terminal debugger commands don't always work. (Dominique Pelle)
Solution: Set 'cpo' to its default value when defining comm

patch 8.1.0195: terminal debugger commands don't always work

Problem: Terminal debugger commands don't always work. (Dominique Pelle)
Solution: Set 'cpo' to its default value when defining commands. (Christian
Brabandt)

show more ...

patch 8.1.0193: terminal debugger buttons don't always work

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 point

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 running

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 running

Problem: MS-Windows: Cannot interrupt gdb when program is running.
Solution: Add debugbreak() and use it in the terminal

patch 8.1.0091: MS-Windows: Cannot interrupt gdb when program is running

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.

show more ...

patch 8.1.0089: error when ending the terminal debugger

Problem: error when ending the terminal debugger
Solution: Fix deleting defined signs for breakpoints. Make the debugger
wor

patch 8.1.0089: error when ending the terminal debugger

Problem: error when ending the terminal debugger
Solution: Fix deleting defined signs for breakpoints. Make the debugger
work better on MS-Windows.

show more ...

patch 8.1.0081: the terminal debugger doesn't adjust to changed 'background'

Problem: The terminal debugger doesn't adjust to changed 'background'.
Solution: Add an OptionSet autocommand. (Chri

patch 8.1.0081: the terminal debugger doesn't adjust to changed 'background'

Problem: The terminal debugger doesn't adjust to changed 'background'.
Solution: Add an OptionSet autocommand. (Christian Brabandt)

show more ...

patch 8.1.0080: can't see the breakpoint number in the terminal debugger

Problem: Can't see the breakpoint number in the terminal debugger.
Solution: Use the breakpoint number for the sign. (Ch

patch 8.1.0080: can't see the breakpoint number in the terminal debugger

Problem: Can't see the breakpoint number in the terminal debugger.
Solution: Use the breakpoint number for the sign. (Christian Brabandt)

show more ...

patch 8.1.0071: terminal debugger only works with the terminal feature

Problem: Terminal debugger only works with the terminal feature.
Solution: Make it also work with a prompt buffer. Makes

patch 8.1.0071: terminal debugger only works with the terminal feature

Problem: Terminal debugger only works with the terminal feature.
Solution: Make it also work with a prompt buffer. Makes it possible to use
on MS-Windows. Various other improvements. (closes #3012)

show more ...

patch 8.0.1725: terminal debugger doesn't handle command arguments

Problem: Terminal debugger doesn't handle command arguments.
Solution: Add the :TermdebugCommand command. Use a ! to execute

patch 8.0.1725: terminal debugger doesn't handle command arguments

Problem: Terminal debugger doesn't handle command arguments.
Solution: Add the :TermdebugCommand command. Use a ! to execute right away.
(Christian Brabandt)

show more ...

patch 8.0.1713: terminal debugger doesn't handle arguments

Problem: Terminal debugger doesn't handle arguments.
Solution: Use <f-args> and pass all the arguments to gdb, e.g. the core file

patch 8.0.1713: terminal debugger doesn't handle arguments

Problem: Terminal debugger doesn't handle arguments.
Solution: Use <f-args> and pass all the arguments to gdb, e.g. the core file
or process number. (suggested by Christian Brabandt) Disallow
starting the debugger twice.

show more ...

patch 8.0.1668: terminal debugger: can't re-open source code window

Problem: Terminal debugger: can't re-open source code window.
Solution: Add the :Source command. Also create the window if n

patch 8.0.1668: terminal debugger: can't re-open source code window

Problem: Terminal debugger: can't re-open source code window.
Solution: Add the :Source command. Also create the window if needed when
gdb stops at a source line.

show more ...

patch 8.0.1655: outdated gdb message in terminal debugger unclear

Problem: Outdated gdb message in terminal debugger unclear.
Solution: Specifically mention the required gdb version. Avoid get

patch 8.0.1655: outdated gdb message in terminal debugger unclear

Problem: Outdated gdb message in terminal debugger unclear.
Solution: Specifically mention the required gdb version. Avoid getting
stuck on pagination.

show more ...

patch 8.0.1599: no error message when gdb does not support debugger

Problem: No error message when gdb does not support the terminal debugger.
Solution: Check for the response to open the Machi

patch 8.0.1599: no error message when gdb does not support debugger

Problem: No error message when gdb does not support the terminal debugger.
Solution: Check for the response to open the Machine Interface.

show more ...

patch 8.0.1562: the terminal debugger can't set a breakpoint with the mouse

Problem: The terminal debugger can't set a breakpoint with the mouse.
Solution: Add popup menu entries.

Updated runtime files.

Add Serbian translations and spell checking.

Update runtime files

patch 8.0.1318: terminal balloon only shows one line

Problem: Terminal balloon only shows one line.
Solution: Split into several lines in a clever way. Add balloon_split().
Make ba

patch 8.0.1318: terminal balloon only shows one line

Problem: Terminal balloon only shows one line.
Solution: Split into several lines in a clever way. Add balloon_split().
Make balloon_show() accept a list in the terminal.

show more ...

patch 8.0.1309: cannot use 'balloonexpr' in a terminal

Problem: Cannot use 'balloonexpr' in a terminal.
Solution: Add 'balloonevalterm' and add code to handle mouse movements in a
t

patch 8.0.1309: cannot use 'balloonexpr' in a terminal

Problem: Cannot use 'balloonexpr' in a terminal.
Solution: Add 'balloonevalterm' and add code to handle mouse movements in a
terminal. Initial implementation for Unix with GUI.

show more ...

patch 8.0.1293: setting a breakpoint in the terminal debugger sometimes fails

Problem: Setting a breakpoint in the terminal debugger sometimes fails.
Solution: Interrupt the program if needed.

patch 8.0.1293: setting a breakpoint in the terminal debugger sometimes fails

Problem: Setting a breakpoint in the terminal debugger sometimes fails.
Solution: Interrupt the program if needed. Set the interface to async.

show more ...

Update runtime files.

patch 8.0.1264: terminal debugger gets stuck in small window

Problem: Terminal debugger gets stuck in small window.
Solution: Add "-quiet" to the gdb command. (Christian Brabandt, closes #2154)