[hackers] [scroll] discribe the current status of scroll || Jan Klemkow

From: <git_AT_suckless.org>
Date: Mon, 18 Jan 2021 21:50:35 +0100 (CET)

commit d3d81f46445c69af661102ece1979c880724415e
Author: Jan Klemkow <j.klemkow_AT_wemelug.de>
AuthorDate: Mon Jan 18 21:42:06 2021 +0100
Commit: Jan Klemkow <j.klemkow_AT_wemelug.de>
CommitDate: Mon Jan 18 21:49:16 2021 +0100

    discribe the current status of scroll

diff --git a/README b/README
index 0b5d954..9cb59d2 100644
--- a/README
+++ b/README
_AT_@ -7,6 +7,23 @@ productive use.
 The initial version of this program is from Roberto E. Vargas Caballero:
         https://lists.suckless.org/dev/1703/31256.html
 
+What is the state of scroll?
+
+The project is faced with some hard facts, that our original plan is not doable
+as we thought in the fist place:
+
+ 1. [crtl]+[e] is used in emacs mode (default) on the shell to jump to the end
+ of the line. But, its also used so signal a scroll down mouse event from
+ terminal emulators to the shell an other programs.
+
+ - A workaround is to use vi mode in the shell.
+ - Or to give up mouse support (default behavior)
+
+ 2. scroll could not handle backward cursor jumps and editing of old lines
+ properly. We just handle current line editing and switching between
+ alternative screens (curses mode). For a proper end user experience we
+ would need to write complete new terminal emulator like screen or tmux.
+
 What is the performance impact of scroll?
 
         indirect OpenBSD
Received on Mon Jan 18 2021 - 21:50:35 CET

This archive was generated by hypermail 2.3.0 : Mon Jan 18 2021 - 22:00:39 CET