feat(session-picker): add full message preview with formatter rendering#398
Conversation
jensenojs
force-pushed
the
feat/session-picker-preview-v2
branch
from
cbbb455 to
67c3130
Compare
|
After testing this, I really like this. A little nitpick is the line numbers, in the preview 
It would look better without them 
A part from that once the conflict is resolved and the code is rebased, it should be good to go. |
- base_picker: add preview='custom' + preview_fn type, Telescope buffer_previewer implementation for custom content preview - output_window: extract apply_extmarks(bufnr, extmarks, line_offset?) as reusable public function; set_extmarks delegates to it - api_client: list_messages(id, directory, opts?) accepts opts table for query parameters (e.g. limit) - session: get_messages(session, opts?) passes opts through
Session picker now shows a rich preview when selecting a session: - normalize_message_order: handle API descending order - filter_preview_messages: show first user msg + last assistant reply - format_messages: reuse existing formatter for consistent rendering (pcall per-part, no get_child_parts, no previous_message) - render_preview_buffer: direct nvim API with window-local folds - preview_fn: synchronous load via Promise:wait() (~20-30ms) Only Telescope backend supported in this commit.
- Unify custom preview rendering behind a backend-neutral preview target so session previews work consistently with Telescope, fzf-lua, and Snacks. - Normalize picker plugin aliases such as fzf-lua, telescope.nvim, and snacks.nvim to their internal backend names, and add regression coverage for custom preview behavior across the picker integrations.
jensenojs
force-pushed
the
feat/session-picker-preview-v2
branch
from
67c3130 to
5634272
Compare
plz try again, I'm a bit too lazy to reproduce this locally. For some reason, my telescope doesn't have this issue, but if it did, I'd definitely fix it. |
|
I still have some minor improvements and optimizations I want to make, but I need to take a break. Not sure when I'll tinker with this plugin next, maybe soon. |
|
Thank you very much it works really great now :). I think we can merge this and, if there is any other optimization to be done we can add them later. |
|
Just shove it somewhere, I don't want this issue to be closed, lol |
2 participants
base on #393, to close #391
just for try out, @sudo-tee