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

minor nuisance: separate text blocks with empty lines #766

Closed
3 tasks done
lervag opened this issue May 2, 2023 · 5 comments
Closed
3 tasks done

minor nuisance: separate text blocks with empty lines #766

lervag opened this issue May 2, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@lervag
Copy link
Contributor

lervag commented May 2, 2023

Did you check docs and existing issues?

  • I have read all the lazy.nvim docs
  • I have searched the existing issues of lazy.nvim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.0

Operating system/version

Arch Linux

Describe the bug

In the Sync screen, I've noticed that the } key does not move between the different blocks. This is because the blocks of text are separated by lines with one or more spaces. Would it be possible to make a minor update that ensures that the blocks of text are separated by empty lines?

The below shows what I mean and is the result of /^\s\+$:

image

Let me know if you find this request unclear.

Steps To Reproduce

Do :Lazy sync and observe that the lines that separate blocks are not empty, but instead contains two spaces.

Expected Behavior

Lines that separate blocks should be empty.

Repro

No response

@lervag lervag added the bug Something isn't working label May 2, 2023
@folke
Copy link
Owner

folke commented May 2, 2023

not a fan of this

@folke folke closed this as not planned Won't fix, can't repro, duplicate, stale May 2, 2023
@lervag
Copy link
Contributor Author

lervag commented May 2, 2023

Uhm, sorry, but could you explain why? Is there any reason to not make the suggested change?

I could look into the code and suggest a PR if you don't want to spend the time, but I won't do that if you'll reject the change.

@folke folke reopened this May 2, 2023
@folke
Copy link
Owner

folke commented May 2, 2023

Sorry,looks like I didn't read your issue report correctly. Feel free to make a pr. Thanks

@lervag
Copy link
Contributor Author

lervag commented May 2, 2023

Ok, glad to hear it. I don't want to change how anything looks, I only want to keep the "empty lines" actually empty. That way, navigation with e.g. } and { works as expected, among other things.

I'll try and figure out how to solve this and open a PR. I'll let you know if I need help.

@lervag
Copy link
Contributor Author

lervag commented May 2, 2023

Let's continue the discussion in #768.

@lervag lervag closed this as completed May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants