On 24/06/12 11:59 AM, Christian Brabandt wrote:
On Mi, 12 Jun 2024, Ernie Rael wrote:
I used termdebug yesterday for some real work. Before opening issues, I'd
like to verify/check if these are old/new issues; I don't remember having
seen them, so I'm thinking new. Is there a convenient way to run the old and
new side by side?
Some things I saw yesterday are
* stack up/down occasionally takes around two seconds
* current execution line, or frame current line, not always highlighted
* E1013: Argument 1: type mismatch, expected number but got string
* Error detected while processing BufRead Autocommands for
"*"..function <SNR>41_BufRead:
These could all be a single problem. I have a pretty vanilla setup...
Those are probably fallout from the recent conversion to Vim9 script.
Right, is there a convenient way to run the pre-conversion termdebug,
without getting rid of the new one. I want to provide accurate issue
reports. (and if needed ...)
-ernie
Thanks,
Christian
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/eb19cfee-cc3e-44ab-8ffc-8e3f1d56db97%40raelity.com.
