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

Vim Mode: regression of "o"-cmd #3931

Closed
lockejan opened this issue Oct 16, 2020 · 3 comments
Closed

Vim Mode: regression of "o"-cmd #3931

lockejan opened this issue Oct 16, 2020 · 3 comments
Labels
bug It's a bug

Comments

@lockejan
Copy link

When using the o-cmd in vim mode adds another line and moves with the cursor to it as expected but it doesn't enter insert mode then.
This used to work but it's not anymore.
So instead of switching to insert mode one stays in command mode.

Environment

Joplin version: Joplin 1.2.6
Platform: macOS
OS specifics: Catalina 10.15.7 (19H2) - installed via homebrew

Steps to reproduce

  1. Activate vim-mode
  2. Open a note and hit o
  3. cursor move to a new line under the current position (but stays in cmd mode)

Describe what you expected to happen

Adding another line at cursor position and switching to insert mode.

Logfile

The logs and console outputs aren't including any errors or warnings. This seems to be rather an logical bug than anything else.

@lockejan lockejan added the bug It's a bug label Oct 16, 2020
@laurent22
Copy link
Owner

Is that what this pull request is fixing? #3897

@lockejan
Copy link
Author

Is that what this pull request is fixing? #3897

Yes, indeed.👍
Didn't see it while I was searching for a similar issue. Thx.

@CalebJohn
Copy link
Collaborator

Just a tip when searching for previous issues. Try to keep the search as vague as possible while remaining on topic. For example, if you search for "vim" using the gihub search, 4 of the first 6 matches are duplicates of this issue. All titles are some variation of "vim is broken". This won't work in all cases, but it's a good starting point for most issue searches.

Anyways, thanks for the report, I'll close this now.

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

No branches or pull requests

3 participants