-
Notifications
You must be signed in to change notification settings - Fork 29
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
V should wrap long lines #245
Labels
Comments
burnsauce
changed the title
V should handle long lines
V / Interpret should handle long lines
Mar 19, 2020
burnsauce
changed the title
V / Interpret should handle long lines
V should wrap long lines
Mar 19, 2020
Agreed! This would be good to have!
…On Thu, 19 Mar 2020 at 23:05, Poindexter Frink ***@***.***> wrote:
I'm not sure what the correct solution is, but I am increasingly feeling
like V should handle long lines without issue, probably via soft wrapping.
The current idiom of manually wrapping files included on the disk and
relying on all opened files to have been treated so (or simply created with
a compliant V) limits V substantially.
Consider that the 34 characters that can be entered as an s" in V is 6 shy
of a full line of text output. While some applications can factor this
away, there may be a full line of literal text (or more) that you may want
to enter, perhaps as a data string.
I understand that this will introduce the seemingly-confusing behaviour of
navigating vertically not always being a line at a time, but this would be
keeping with vim.
I think it would make coding a bit more fluid, as you don't have to look
ahead to see if a word will fit. I know I've miscalculated that limit
before. A soft wrap would be welcome here.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#245>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAY34O44JHBIIJEDG75TJILRIKJL5ANCNFSM4LPW4UBQ>
.
|
Isn't it largely a matter of making sure the line link table is properly set? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure what the correct solution is, but I am increasingly feeling like V should handle long lines without issue, probably via soft wrapping.
The current idiom of manually wrapping files included on the disk and relying on all opened files to have been treated so (or simply created with a compliant V) limits V substantially.
Consider that the 34 characters that can be entered as an s" in V is 6 shy of a full line of text output. While some applications can factor this away, there may be a full line of literal text (or more) that you may want to enter, perhaps as a data string.
I understand that this will introduce the seemingly-confusing behaviour of navigating vertically not always being a line at a time, but this would be keeping with vim.
I think it would make coding a bit more fluid, as you don't have to look ahead to see if a word will fit. I know I've miscalculated that limit before. A soft wrap would be welcome here.
edit: sorry for the edit spam. Misdiagnosed an interpreter error momentarily.
The text was updated successfully, but these errors were encountered: