John C F

A fork to support Vim-with-channels

3

Basically, these 3 files have to be re-implemented: - [`autoload/lldb/remote.vim`](https://github.com/critiqjo/lldb.nvim/blob/master/autoload/lldb/remote.vim): This is responsible for sending all events to the backend. This needs to be replaced with something which encodes these...

Define debugger-generic event-based interface

2

Separate out LLDB-specific logic and define a debugger-generic event-based interface. This will enable adding support for other debuggers using output parsing (e.g. GDB support can be added by borrowing parser...

The reason for choosing [`abspath`](https://github.com/critiqjo/lldb.nvim/blob/b8d2422/rplugin/python/lldb_nvim/controller.py#L211) was because breakpoints did not seem to work while debugging Rust programs (back when Rust was 1.0 or 1.1). Need to reinvestigate.

Feature: Interactive buffers

3

Ability to - From the breakpoints buffer - [x] Delete breakpoints - [ ] Enable/disable breakpoint locations - [ ] Jump to breakpoint locations (useful?) - [x] Select thread and...

Ideas (as extension to #7): - Ability to execute shell commands during mode switch - Record and create custom modes (without manually editing session file)

Separation of Core and UI

5

_Assumptions:_ Single window, single file ### Concerns of Core - Buffer (text) management - Typesetting (constrained to a viewport dimensions RxC) - Command handling - Key-mappings - Cursor movements etc....