bug: no way to get to the normal mode

[dmtrKovalenko]

Prerequisites

• I searched the docs
• I searched existing issues

:checkhealth opencode output

there is no problem

Describe the bug

PLEASE get me back my normal mode it was the only reason I used this plugin, it used to work now this thing is completely erased #151 I can not navigate the buffer

• now esc is not actually working, I have to pin the old version that now conflicts with the new opencode versions

Steps To Reproduce

1. toggle opencode
2. try to press esc or any other binding to exit to normal mode (it doesn't wokr)
3. try to use

Expected Behavior

the way it used to work right after this PR got merged -> #151

[nickjvandyke]

As opencode.nvim approaches v1.0, I removed the terminal integration because it's out of scope and proved too much maintenance burden. See a7c4dd7 for details.

I have to pin the old version that now conflicts with the new opencode versions

I don't think OpenCode has had any breaking API changes since then. That version of the plugin should work fine with it. The health version check is just for insurance.

I understand it's an important feature to you though, and fortunately you can add it to your personal config 🙂 Simply customize vim.g.opencode_opts.start (or however you launch your OpenCode terminal) to register the buffer keymaps as you did in plugin code in #151. opencode.nvim still exposes the requisite command API.

Let me know if that doesn't work. Thanks for understanding!

[dmtrKovalenko]

I am more mad why are you breaking my workflow with every update? Why do you make a breaking changes without prior notice?

The plugin should work without changing configuration.

[dmtrKovalenko]

And I do not understand why did you remove the feature that is clearly beneficial for every neovim user.

The fact that you don't use doesn't mean that other people won't use it.

[nickjvandyke]

Why do you make a breaking changes without prior notice?

Breaking changes are noted in the changelog, release notes, and semantic versioning. It's up to you to read those and decide when to update. I understand there are many breaking changes lately as I figure out what to bring into v1.0. Sorry about that! But 0.x versions are implicitly unstable and breaking changes should be expected.

And I do not understand why did you remove the feature that is clearly beneficial for every neovim user.

I already gave my reasoning in my prior comment. 🙂