From: kalterdev@gmail.com
To: 9fans <9fans@9fans.net>
Subject: [9fans] Re: Bug: Acme: very long lines scroll by one character
Date: Mon, 30 Sep 2024 18:23:14 -0400 [thread overview]
Message-ID: <17277349940.2eE0dD4e.423778@composer.9fans.topicbox.com> (raw)
In-Reply-To: <17277346280.4Def3.29849@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
> Any long line could work.
To be specific, 1100 characters is enough.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf973120ebf6f0710-M71dc8d6676a11a98d6bc96e6
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1409 bytes --]
next prev parent reply other threads:[~2024-09-30 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 22:17 [9fans] " kalterdev
2024-09-30 22:23 ` kalterdev [this message]
2024-10-01 9:31 ` [9fans] " Noam Preil
2024-10-01 10:27 ` [9fans] " Emery Hemingway
2024-10-01 12:09 ` kalterdev
2024-10-01 13:00 ` Emery Hemingway
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=17277349940.2eE0dD4e.423778@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).