Jan Ph. H.
Jan Ph. H.
If you use the default behavior (shell), then this is the default behavior of neovim inbuild shell and a duplicate of #202 and possibly related to make it less annoying...
> Neovim doesn't either Unfortunately rr does not work at my workplace. > you would want a REPL-like behaviour for gdb I dont understand how internally nvim-gdb stores debug points...
Cool, this looks perfect for my use case. Thanks a lot!
I think what I actually want is an editable scratch buffer with the gdb command history and a command to load the current actual history into a scratch buffer. I...
Some observations during playing around: - 1. storing and loading breakpoints dynamically is as simple as `save breakpoints tmp` and `source tmp`. - 2. Trying to run gdb -x /tmp/histfile...
https://stackoverflow.com/a/40311142 `os.path.realpath(os.path.expanduser('~/subdir/../data'))`should work, if it uses [realpath on macos](https://developer.apple.com/library/archive/documentation/System/Conceptual/ManPages_iPhoneOS/man3/realpath.3.html). However, I cant say much on what python uses internally with what fallback code for compatibility. Startup perf of perl should...
Can you tell me how you would like to store and load persistent state of project paths of nvim-gdb? See also #180. Some notes on the user-options: I think its...
@Th3Whit3Wolf Found the reason why. I guess this was changed upstream in colorbuddy.nvim at some point, but not documented: https://github.com/tjdevries/colorbuddy.nvim/issues/17 Would be nice to document in usage of all your...
For further inspiration of async loading stuff or using treesitter colorgroups consider stealing from glepnir: https://github.com/glepnir/zephyr-nvim/blob/main/lua/zephyr.lua