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

Bad handling of newlines in paragraph text objects #1989

Closed
brandonbloom opened this issue Aug 30, 2017 · 0 comments
Closed

Bad handling of newlines in paragraph text objects #1989

brandonbloom opened this issue Aug 30, 2017 · 0 comments

Comments

@brandonbloom
Copy link
Contributor

  • 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.


What happened:

Deleting paragraph text objects does match the behavior of vim. It's also not self-consistent between visual+motion+delete vs delete+motion.

Open a new file, type in this:

1
2

3
4
5

6
7

Place cursor on '4', type dap. You'll get:

1
2


6
7

Notice two blank lines. The cursor will be on the second blank line.

What did you expect to happen:

There should be one blank line and the cursor should be on the '6'.

1
2

6
7

How to reproduce it:

You can get the correct behavior if instead of dap, you use vapd.

Note that dip is similarly broken.

brandonbloom added a commit to brandonbloom/vscode-vim that referenced this issue Sep 2, 2017
@Chillee Chillee closed this as completed in 4d11098 Sep 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant