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

Jump to bottom

Paragraph motions should ignore whitespace #222

Open
GoogleCodeExporter opened this issue Aug 18, 2015 · 2 comments
Open

Paragraph motions should ignore whitespace #222

GoogleCodeExporter opened this issue Aug 18, 2015 · 2 comments
Labels
auto-migrated defect enhancement patch Priority-Medium

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Insert text with paragraphs separated by lines consisting of a single space 
character.
2. Use { and } to skip between paragraphs.

What is the expected output? What do you see instead?

The { and } motions should stop at the whitespace only lines. This is 
consistent with the paragraph text-object which delimits paragraphs with 
whitespace only lines.

What version of the product are you using? On what operating system?

7.4, Linux

Please provide any additional information below.

Wrapping the ml_get() call in startPS() (in search.c) with skipwhite() fixes 
the problem. If we're worried about backward compatibility perhaps a flag could 
be used to turn this behavior on.

Original issue reported on code.google.com by matthewe...@gmail.com on 8 May 2014 at 9:17

Attachments:
@GoogleCodeExporter
Copy link
Author 

Hey,

I did some research for you. Previous disco @

https://groups.google.com/d/msg/vim_dev/8HShAdoMUSw/CmETEeArSVUJ
https://groups.google.com/d/msg/vim_use/eMRBf_7nj50/4od47U3bpb4J
https://groups.google.com/d/msg/vim_use/2GJQFanj4mE/4xLlx52o73QJ

Best,

Original comment by 676c7...@gmail.com on 8 May 2014 at 2:52

@GoogleCodeExporter
Copy link
Author 

Thanks for the info. I'll be sure to check the mailing lists in future before 
reporting a bug (I wasn't aware of the correct procedure).

It looks like the first thread died even though a patch was suggested? Anyway, 
it could be that using a plugin (eg. 
http://www.vim.org/scripts/script.php?script_id=3952) may be the best option to 
avoid excessive changes to the core.

Original comment by matthewe...@gmail.com on 9 May 2014 at 9:15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated defect enhancement patch Priority-Medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrisbra @GoogleCodeExporter