[vim/vim] message "[termdebug] Termdebug already loaded." (Issue #15256)

step

unread,

Jul 13, 2024, 6:51:30 PM7/13/24

to vim/vim, Subscribed

I think the following paragraph establishes the point that vim 9.1.0580 doesn't automatically load the termdebug plugin, consistently with prior versions and withe help file.

Start with an empty vimrc file in an otherwise empty ~/.vimrc configuration directory. The :Termdebug command can't be found until you type :packadd termdebug in the vim command line.

Now exit vim and append the following line to the otherwise empty ~/.vim/vimrc file:

packadd termdebug

and run vim. A new error message temporarily holds vim startup:

[termdebug] Termdebug already loaded.
Press ENTER or type command to continue

(Side note: perhaps this message is useful but it's certainly annoying).
So why is the plugin already loaded if we established that vim doesn't load it automatically? How can I load the termdebug plugin from vimrc without errors?

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

step

unread,

Jul 14, 2024, 3:00:47 AM7/14/24

to vim/vim, Subscribed

Following the "already loaded" message, if I then execute :Termdebug vim shows the following error message:

E117: Unknown function: StartDebug

and does not start the debugger.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

ubaldot

unread,

Jul 14, 2024, 4:12:06 AM7/14/24

to vim/vim, Subscribed

Thanks for reporting. I will look into that asap.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jul 14, 2024, 4:12:08 AM7/14/24

to vim/vim, Subscribed

as mentioned in a different issue, you need to use packadd! termdebug inside your vimrc file

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

step

unread,

Jul 14, 2024, 4:23:21 AM7/14/24

to vim/vim, Subscribed

Thank you. I can confirm that it works OK with packadd!. If this is the final solution, may I suggest to mention the remedy in help termdebug-starting.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

ubaldot

unread,

Jul 14, 2024, 4:30:27 AM7/14/24

to vim/vim, Subscribed

as mentioned in a different issue, you need to use packadd! termdebug inside your vimrc file

@chrisbra the link does not seem to work. I would be genuinely curious why the ! is needed :)

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

step

unread,

Jul 14, 2024, 4:33:10 AM7/14/24

to vim/vim, Subscribed

@ubaldot does this link work for you? #15058

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jul 14, 2024, 4:37:55 AM7/14/24

to vim/vim, Subscribed

@chrisbra the link does not seem to work. I would be genuinely curious why the ! is needed :)

It's documented at :h packadd ;)

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jul 14, 2024, 4:43:00 AM7/14/24

to vim/vim, Subscribed

Closed #15256 as completed via 27c5598.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward