Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for vterm-mode doesn't seem to work anymore #113

Closed
aspiwack opened this issue Apr 3, 2021 · 2 comments
Closed

Support for vterm-mode doesn't seem to work anymore #113

aspiwack opened this issue Apr 3, 2021 · 2 comments

Comments

@aspiwack
Copy link
Collaborator

aspiwack commented Apr 3, 2021

In the past few weeks or so, I noticed that the special terminal support for vterm (introduced in #88 ) doesn't appear to work any more.

The initial mode is special, so x is captured (and attempting to go in command mode and qx gives a read-only buffer error).

I have no real idea when this changed. But it doesn't seem to affect other terminal modes (I've tried ansi-term, and it works fine).

Cc @tomterl

@jyp
Copy link
Owner

jyp commented Apr 13, 2021

Unfortunately I can't reproduce the problem. My 'vterm' buffer is not special.

@aspiwack
Copy link
Collaborator Author

Thanks to your answer I figured out what was wrong. I had a customised boon-special-mode-list which was from way back and messed things up. I don't know why it just started to act up though. But it's solved. Thanks. And sorry for the noise 🙁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants