| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Problem: Cursorline highlighting always overrules sign highlighting.
Solution: Combine the highlighting, use the priority to decide how.
(closes #6812)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
Problem: Terminal debugger plugin may hang.
Solution: Wait longer when still reading symbols.
|
|
|
|
|
|
|
|
Problem: Terminal debugger does not handle unexpected debugger exit.
Solution: Check for debugger job ended and close unused buffers. (Damien)
|
|
Problem: Termdebug: clearing multi-breakpoint does not work.
Solution: Delete all X.Y breakpoints. Keep more information about placed
breakpoints. (Ozaki Kiichi, closes #3641)
|
|
Problem: Termdebug: gdb may use X.Y for breakpoint number.
Solution: Handle X.Y breakpoint numbers. (Yasuhiro Matsumoto, close #3641)
|
|
|
|
Problem: Terminal debugger error with .gdbinit file.
Solution: Check two lines for the "new ui" response. (hint from Hirohito
Higashi)
|
|
Problem: Terminal debugger commands don't always work. (Dominique Pelle)
Solution: Set 'cpo' to its default value when defining commands. (Christian
Brabandt)
|
|
Problem: Terminal debugger buttons don't always work. (Dominique Pelle)
Solution: Set 'cpo' to its default value.
|
|
Problem: Terminal debugger: error when setting a watch point.
Solution: Don't try defining a sign for a watch point.
|
|
Problem: non-MS-Windows: Cannot interrupt gdb when program is running.
Solution: Only use debugbreak() on MS-Windows.
|
|
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.
|
|
Problem: error when ending the terminal debugger
Solution: Fix deleting defined signs for breakpoints. Make the debugger
work better on MS-Windows.
|
|
Problem: The terminal debugger doesn't adjust to changed 'background'.
Solution: Add an OptionSet autocommand. (Christian Brabandt)
|
|
Problem: Can't see the breakpoint number in the terminal debugger.
Solution: Use the breakpoint number for the sign. (Christian Brabandt)
|
|
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)
|
|
Problem: Terminal debugger doesn't handle command arguments.
Solution: Add the :TermdebugCommand command. Use a ! to execute right away.
(Christian Brabandt)
|
|
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.
|
|
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.
|
|
Problem: Outdated gdb message in terminal debugger unclear.
Solution: Specifically mention the required gdb version. Avoid getting
stuck on pagination.
|
|
Problem: No error message when gdb does not support the terminal debugger.
Solution: Check for the response to open the Machine Interface.
|
|
Problem: The terminal debugger can't set a breakpoint with the mouse.
Solution: Add popup menu entries.
|
|
Add Serbian translations and spell checking.
|
|
|
|
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.
|
|
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.
|
|
Problem: Setting a breakpoint in the terminal debugger sometimes fails.
Solution: Interrupt the program if needed. Set the interface to async.
|
|
|
|
Problem: Terminal debugger gets stuck in small window.
Solution: Add "-quiet" to the gdb command. (Christian Brabandt, closes #2154)
|
|
|
|
|
|
|
|
Problem: Cannot define a toolbar for a window.
Solution: Add a window-local toolbar.
|
