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

Cursor Error when switch window #117

Closed
HsunGong opened this issue Jul 19, 2021 · 2 comments
Closed

Cursor Error when switch window #117

HsunGong opened this issue Jul 19, 2021 · 2 comments
Assignees
Labels
duplicate This issue or pull request already exists verified This issue was already verified

Comments

@HsunGong
Copy link

HsunGong commented Jul 19, 2021

General information

iterm 3.4.3
zsh5.8
os macos
tmux 2021

Basic examination

When open 2 terminal window in tmux,
In first terminal, we use zsh with vi-insert mode;
In the second terminal, we then open a vim window;
Found that the vim cursor is changed based on the first window, shown in the picture.

image

Expected behavior

In vim window, we want block cursor rather than underline/beam.

reproduction

1, ZVM_INSERT_MODE_CURSOR=$ZVM_CURSOR_BEAM or $ZVM_CURSOR_UNDERLINE

2, tmux with 2 panes in ONE window.

3, in pane ONE: toggle insert mode in zsh-vi-mode
image

4, in pane TWO: use vim to open a file(no mode requirements<INSERT/NORMAL> is ok).
image

5, see vim file: the cursor is changed to BEAM or UNDERLINE as the picture.

image

6, if does not reproduced, use this:

enter pane ONE: enter insert mode(to get underline/beam)
reenter pane TWO with vim: find underline/beam in vim.

@HsunGong HsunGong changed the title Cursor Cursor Error when switch window Jul 19, 2021
@jeffreytse jeffreytse self-assigned this Jul 19, 2021
@jeffreytse jeffreytse added verified This issue was already verified duplicate This issue or pull request already exists labels Jul 19, 2021
@jeffreytse
Copy link
Owner

@HsunGong, this issue is the same as another issue #11.

@HsunGong
Copy link
Author

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists verified This issue was already verified
Projects
None yet
Development

No branches or pull requests

2 participants