Line wrapping for documents #123
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#123
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have been over this a few times so sorry if this has already been covered.
When viewing the document gopher://baud.baby:70/0/phlog/fs20191226.txt in bombadillo, the first and second lines wrap what seems to be empty space with the terminal at 80 characters wide. Downloading and viewing this document in vim or less does not show this wrapping.
It's possible to reproduce this behaviour by setting the terminal width to 80 characters, then viewing a document with 80 characters per line. I've just tested using ASCII characters - an example I used with underscores as the 80th character:
This does not relate to #35 which was a very similar situation. That document displays correctly now.
Was there something recently about wrapping slightly early to avoid issues with some really wide characters? I couldn't find this issue to refer to it.
This is indeed caused by wrapping to one less than the width.
This can be fixed by making the
<
into a<=
here: https://tildegit.org/sloum/bombadillo/src/branch/master/page.go#L80Before opening a PR I want to make sure that this does not affect the render method(s) or the main draw method. Once I have verified that I will open a PR.
I think once this goes in and the other two that are open PRs currently I may call that 2.1.0 and move develop into master. Maybe? A good number of features and bug fixes have built up and are available to people pulling develop, but it would be good to have them on master.
I thought I had included this in the recent merge of 2.1.0. It seems I did not. I will get this updated soon, sorry for letting the issue sit so long!
@asdf Are you able to confirm if this has been fixed? This has been on here awhile and I had thought this got merged in but now I am unsure.
I've retested using the document mentioned and the issue is resolved. Thank you!