From 830aa98067d1c3f0a88bfbcae0ef9acfdc6b3ff0 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Sun, 26 Jul 2026 22:40:22 -0300 Subject: next-next-steps: new feature list --- next-next-steps.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/next-next-steps.txt b/next-next-steps.txt index 00b0711f..412e4dd1 100644 --- a/next-next-steps.txt +++ b/next-next-steps.txt @@ -1,2 +1,5 @@ -- Editing mode on pty pane should behave the same as if it was a regular text file. You should implement tests that will send the same commands to the same text buffer, but one is a pty and one is a file pane and the result after chaning should be the same. Right now I can't create new lines freely nor split current lines; this might require some refactoring because the pty editing was done in a real simple way. -- Add builtins (that work with 0 args by default) that are reachable via SPC, so like SPC+? will open the Help builtin that will list all bultins that start with the prefix command after SPC and before ?; SPC+h+t will trigger the tutor builtin, SPC+d will be the Del, SPC+k will be the kill (the only new one for now will be the Help builtin) +- in normal mode in a output pane pressing Esc should call a Del on that pane. +- add SPC-f-f builtin Find that will work the same way as calling fd (you should implement it like / for search on text files) n/N semantics should just work, if they don't you need to refactor +- add window navigation builtins: SPC-w-h SPC-w-j SPC-w-k SPC-w-l, and SPC-w-t (toggle terminal, will toggle the focus between the latest file pane and the latest termianal pane) +- when opening stuff, like yazi or something some debug text (probably from vaxis?) is printed - this should be hidden. You need to find this and fix it. +- by default the images will have all that image-specific builtins hidden from the tagline, and the main top tagline will not have the Crt and Colors builtins as well; \ No newline at end of file -- cgit v1.3