lambdalisue/jupyter-vim-binding

The cursor in vim mode covers two letters' width

Open

#143 opened on Apr 23, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (2,062 stars) (139 forks)batch import
help wanted

Description

Summary

Hello, I found the cursor in vim mode covers two letters' width, which is misleading. image

How can I address that ? Thank.

Environment

  • Operating system : remote Ubuntu 16.04 server
  • Web browser : local chrome 73.0.3683.103
  • Version or revision of Jupyter Notebook : 4.4.0 with Python 2.7.15
  • Revision of jupyter-vim-binding : c9822c75

Behavior

As the figure shows, the cursor in vim mode covers two letters' width.

Expected

Actual

Step by step procedure

  1. Start local Jupyter Notebook by jupyter notebook
  2. Access http://localhost:8888/
  3. etc.

What you have done to solve the issue

For example, the behavior is confirmed with Firefox 44.0.2 and Google Chrome xx.xx.xx and could not be reproduced in Firefox but Chrome or what ever.

Remarks

If any

Contributor guide

Tech stack
javascriptcss
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
CSSbrowser devtools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the cursor width in vim mode by examining the CSS rules applied to the cursor element. Look for any width or letter spacing properties in the repository's stylesheets that might cause the cursor to cover two letters. The issue was reported in 2019 with no activity, so also check if the bug persists in the current version of the extension.