How to use the old termdebug

[Ernie Rael]

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...

-ernie

[Christian Brabandt]

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.

Thanks,
Christian
--
To have died once is enough.
-- Publius Vergilius Maro (Virgil)

[Ernie Rael]

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

[Ernie Rael]

I've got a patch which includes both the legacy and vim9script termdebug. I set it up so by default one gets the legacy version. If you want the new version, you can something like:

gvim -c "set co=220" -c "packadd termdebug9" -c "Termdebug9 $cmd $core"

I did it like this so existing users get the more reliable version that they are familiar with.

But, given the state of the tree, it's cleaner to add legacy as termdebug8 (or whatever). But if someone runs into trouble with the vim9 version, they won't know about how to use the old one. It's simple to PR either way.

There's only two very small outstanding PRs against the current setup, so that shouldn't be an issue. If needed I can port them

fix: [termdebug] id/subid maybe mis-match type #15015
fix: [termdebug] correct K/-/+ mappings check #15013

Comments/preferences/suggestions appreciated.

-ernie

--
--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/53f865db-defc-42fd-b9ed-f7b33f77a4ca%40raelity.com.