[
https://issues.apache.org/jira/browse/GUACAMOLE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891637#comment-17891637
]
Corentin Soriano commented on GUACAMOLE-1256:
---------------------------------------------
[~shineyoung] I am unable to reproduce this issue.
I have just tested on these 3 VMs with files of different sizes and with
different scrolloff values:
{code:java}
[root@rhel9 ~]# vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb 09 2023 00:00:00)
Included patches: 1-2637
[root@debian ~]# vim --version
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Sep 21 2024 15:03:13)
Included patches: 1-709
[root@rhel8 ~]# vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Aug 5 2022 07:43:09)
Rustines incluses : 1-1763{code}
Have you found a method to reproduce systematically? What OS and version of vim
are you using?
Can you try selecting the "distorted" text to see if the contents of the
clipboard match what is displayed?
> Lines of file gets broken when navigating back and forth using a text editor
> ----------------------------------------------------------------------------
>
> Key: GUACAMOLE-1256
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1256
> Project: Guacamole
> Issue Type: Bug
> Components: Terminal
> Affects Versions: 1.2.0
> Environment: Distributor ID:Ubuntu
> Description:Ubuntu 18.04.2 LTS
> Release:18.04
> Codename:bionic
> Linux dev-kubernetes-01 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Hugaleno Bezerra
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: Screenshot from 2023-10-10 13-39-18.png, Screenshot from
> 2023-10-10 13-41-00.png, bug_scrollingback_onfile.gif,
> image-2024-06-06-18-13-06-244.png
>
>
> Protocol: SSH
> When editing a file using a text editor like vim and navigating back and
> forth in the file some lines get "broken".
> The file being used in the gif below is a default file from ubuntu
> installation "vim /etc/ltrace.conf"
> The problem happens in some servers of our local network, while in anothers
> with same SO it doens't. We tried find a step to step to reproduce the
> problem with 100% accurate but unfortunately we couldn't.
> We decide to share that to see if someone else is having the same problem and
> could help to find the reason.
> If you need any more information to help reproduce de problem pls let me know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
