From: kalterdev@gmail.com
To: 9fans <9fans@9fans.net>
Subject: [9fans] Bug: Acme: Scrolling is not deterministic for long lines
Date: Mon, 30 Sep 2024 11:56:18 -0400 [thread overview]
Message-ID: <17277117780.5c53F.54435@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
Expected behavior
When I scroll with button 3, the line next to the cursor always goes
to the beginning of the visible area. Similarly, If the line is long
and broken (wordwrapped) by Acme, clicking on the line's second part
pushes it to the beginning of the visible area.
Clicking button 1 on the same place must, and in most cases does, pull
the line back to its original place. If the line is long and broken by
Acme, though, button 1 must guarantee that the visible part of the
line goes back.
Unexpected behavior
If the first visible line is long and broken by Acme, button 1 does
not pull it's visible part to the cursor's location.
Steps to reproduce the problem
The problem typically occurs when Acme breaks long lines. Find a long
line, make Acme break it, and scroll with buttons 3 and 1 on the
line's first or second part.
Another weird behavior is exhibited by the first visible line broken
by Acme. Try to scroll it's second part with buttons 3 and 1. On
button 1, the whole line goes to its original place except it's first
character.
See demo for visual demonstration of the two cases.
https://i.imgur.com/S1dyDlU.mp4
Sometimes even the beginning of the long line does not return. I
couldn't identify the exact cause, though, but there's a demo.
https://i.imgur.com/kKNXKC1.mp4
plan9port version
a2567fcac9851e5cc965a236679f568b0e79cff2
OS version
macOS 14.5 (23F79)
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T0539ca6a91adafa6-M94ca138b9ac4a4b4f9bafb2f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2947 bytes --]
reply other threads:[~2024-09-30 15:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17277117780.5c53F.54435@composer.9fans.topicbox.com \
--to=kalterdev@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).