VSCodeVim / VSCodeVim/Vim

Can't type after the pointer came cross a very long line

Open
#2,003 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

  • Click thumbs-up 👍 on this issue if you want it!
  • Click confused 😕 on this issue if not having it makes VSCodeVim unusable.

The VSCodeVim team prioritizes issues based on reaction count.


Is this a BUG REPORT or FEATURE REQUEST? (choose one):

<svg width="15" height="18" viewBox="0 0 15 18" xmlns="http://www.w3.org/2000/svg"><title>Group Copy</title><g fill="none" fill-rule="evenodd"><path d="M7.667 11.222v5.407" stroke="#AAA" stroke-linecap="round"/><path d="M5.699 16.311a.542.542 0 0 1-.406-.182c-1.413-1.582-3.699-1.597-3.746-1.597h-.003a.544.544 0 0 1-.007-1.087c.113-.006 2.813-.003 4.567 1.96a.543.543 0 0 1-.405.906zM9.544 16.312a.543.543 0 0 1-.399-.913c1.816-1.96 4.46-1.959 4.565-1.954a.543.543 0 0 1-.005 1.086H13.7c-.045 0-2.284.015-3.758 1.607a.538.538 0 0 1-.398.174z" fill="#AAA"/><path d="M8.39 12.956H6.666a.533.533 0 0 1-.158-.024c-1.838-.236-3.4-1.302-4.407-3.012C.933 7.933.666 5.36 1.436 3.515a.544.544 0 0 1 .491-.334l.164-.001a7.1 7.1 0 0 1 2.88.582C5.608 2.6 6.334 1.718 7.135 1.136a.55.55 0 0 1 .736.01c.802.59 1.507 1.458 2.146 2.645.897-.405 1.886-.61 2.948-.61l.166.001a.544.544 0 0 1 .491.334c.771 1.845.504 4.418-.666 6.405-1.007 1.709-2.568 2.776-4.406 3.012a.605.605 0 0 1-.16.023z" stroke="#AAA" fill="#FFFCFC"/></g></svg>

Environment:

  • VSCode Version: 1.16.0-insider
  • VsCodeVim Version: 0.10.0
  • OS: macOS

What happened:
I pasted a very long svg code that shrink in one line, after that I couldn't type anymore (it was in insert mode )

What did you expect to happen:

How to reproduce it:
paste a very long one-line code to vscode

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. First reproduce by pasting the supplied very long one-line SVG in VSCodeVim insert mode under the reported VS Code and extension versions; done means typing continues normally afterward, with a regression check for the long-line case.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.