Finite size jump history, improving backtrace, redo, undo grouping, similar for jump history

2025-12-26 15:40:03 +01:00
parent 509db7af46
commit 4221aa8fb7
11 changed files with 84 additions and 23 deletions
--- a/src/backup/todo.txt
+++ b/src/backup/todo.txt
@@ -2,8 +2,6 @@
 - From a user (novice) point of view, how does it look like?

 - Open with seek string (open at pattern) filename:32 filename:/^Window$/
- ctrl+f should insert selected text into search
- Do we need constrained jump history????? So that we can finally collect garbage buffers at some point. Or maybe only constrained to garbage buffers
 - build console window
 - Show what process/coroutines are running and allow to kill (active process buffer?)
 - Database idea: use special buffers to store information