summaryrefslogtreecommitdiff
path: root/features.txt
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-14 21:26:47 -0300
committerGabriel Schneider <[email protected]>2026-09-15 17:24:42 -0300
commita624a56e289e4a02a411f83741f0f2c9fc0f0b2e (patch)
treeb87e3ca10dd1c4417112164f792b5da1e26de0a6 /features.txt
parent95681ff7017b8a9e4c8f9fa6a7371d1233432f2f (diff)
downloadpardes-a624a56e289e4a02a411f83741f0f2c9fc0f0b2e.tar.gz
pardes-a624a56e289e4a02a411f83741f0f2c9fc0f0b2e.zip
Add Linux Tty9p mounted terminals and forward raw TTY keys
Diffstat (limited to 'features.txt')
-rw-r--r--features.txt22
1 files changed, 22 insertions, 0 deletions
diff --git a/features.txt b/features.txt
new file mode 100644
index 00000000..3bfc6967
--- /dev/null
+++ b/features.txt
@@ -0,0 +1,22 @@
+Clicking somewhere and starting editing mode leads to a desync between the click cursor and the edit mode cursor. For the user they should be the same thing
+so if you click somewhere if the cursor moves there the edit cursor should also start there. If its not possible for the edit cursor to be there, then the selection
+cursor must also reflect that and move to a place that is 'close' following some heuristic.
+
+The gui backends should receive events from the mouse4 and mouse5 buttons, the ones from logitech on the thumb that works as page next and page previous on the browser by default. For pardes they should work like ctrl-o and ctrl-i .
+
+Add treesitter context, like lets say that the view is in the middle of the function and we cant se its start, the treesitter context should show on the topmost
+editor line the declaration of the function, it should correctly show the line number and the code highlited, but it should have some tinting on the bg and maybe a
+tiny border on the gui like the tagline has so it looks almost like its the tagline going down a few more rows. It should not just work for functions, but also for struct decls, modules, I'd say any nested declaration that makes sense and you should make sure moving the cursor to there works but it wont move the whole view, but just the cursor and when scrolling up the context declarations will be gradually removed and later you'll find the cursor, it must be seamless. This should be off by default and toggled via a new builtin that will show up on panes where treesitter is active.
+
+The builtins that produce search results like the search and lsp actions and look for files should have some padding between the Location and the result on
+the same like so that the Location results are vertically aligned. There should be a new builtin called LocationsConfig that will return the runtime config used
+by those, like `LocationsConfig context:5 tscontext:on` it will return the structs fields like this and when running the builtin it will parse input in the same
+format using the same comptime info like it used to print the current config, it will only update the keys that were passed. The treesittercontext option
+will show the context like the previous paragraph, but since the lines shown are a subset of the file, the context should be shown in order on the output window (and the location for it should be optional configured by the locationsconfig too). There should also be a context options thats not related to treesitter, to show some lines above and below the match, like grep does.
+
+doing ctrl-o and ctrl-i moves the selection, it should not affect the selection, this is a bug.
+
+on tty mode the mouse selection works but the pardes selection on that pane should follow it, the idea here is that we're trying to make it easier to move text
+between tty panes without changing the pardes semantics or adding anything extra, just neat tricks like this. Still, you might need to come up with something
+to decrease the number of movements/interactions needed to do simple things like copy and pasting text from a terminal to another.
+