no status for operator pending mode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Thank you for this very nice extension.
Describe the bug
When typing y in normal mode, there is no Operator Pending Mode in the status bar. Maybe this is linked to how Escape does not seem to work with operator pending mode in Jupyter notebooks as explained here : https://github.com/VSCodeVim/Vim/issues/7425#issuecomment-1575952639
To Reproduce
-
Open a file (preferably a Jupyter notebook to also see the issue with escape which was mentioned in the previous section)
-
Press
yin normal mode to enter operator pending mode -
See that there is no status indication and that escape acts as though vim is in normal mode and exits the edit cell in Jupyter notebooks (unlike insert or visual mode).
Expected behavior
That it behaves like visual and insert mode showing an indication in the status bar. Moreover, I would expect that escape works with operator pending mode in the same way that it does with insert mode an visual mode in Jupyter notebooks. That is, that it returns to normal mode when pressing escape instead of exiting the cell.
Screenshots
Environment (please complete the following information):
- Extension (VsCodeVim) version: v1.25.2
- VSCode version: 1.78.2
- OS: Linux Fedora
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the missing operator-pending status and Escape behavior in a Jupyter notebook, using the reproduction steps and the linked issue 7425 for context. Trace the status-bar mode indication and notebook Escape handling; done means operator-pending mode is shown and Escape returns to normal mode without exiting the cell.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100