Problem
Right now / opens a search, but only in the chat list pane and only over chat/contact names — it filters which conversation you jump to. Once you're inside a conversation there's no way to find a message: the only option is scrolling back with k / Ctrl-U until you spot it, which gets impractical fast in a chat with any real history.
What I'd like is / (or some other key) inside the conversation pane to search the messages of the currently open chat, with n / N to jump between matches and the matched message brought into view and highlighted. Basically the same interaction the chat-list search already has, just scoped to the open conversation instead.
This is the thing I reach for most often and can't do. Happy to test a branch if you pick it up.
Proposed solution
One thing that might make this cheaper than it looks: the message text is already stored locally. text_messages in the SQLite schema has chat_jid, timestamp and message, so a search could run as a query against what's already on disk rather than needing anything from the server or any new sync. A LIKE over message filtered by chat_jid would probably cover most of what people want, and FTS could come later if it's ever worth it.
Alternatives considered
No response
Problem
Right now
/opens a search, but only in the chat list pane and only over chat/contact names — it filters which conversation you jump to. Once you're inside a conversation there's no way to find a message: the only option is scrolling back withk/Ctrl-Uuntil you spot it, which gets impractical fast in a chat with any real history.What I'd like is
/(or some other key) inside the conversation pane to search the messages of the currently open chat, withn/Nto jump between matches and the matched message brought into view and highlighted. Basically the same interaction the chat-list search already has, just scoped to the open conversation instead.This is the thing I reach for most often and can't do. Happy to test a branch if you pick it up.
Proposed solution
One thing that might make this cheaper than it looks: the message text is already stored locally.
text_messagesin the SQLite schema haschat_jid,timestampandmessage, so a search could run as a query against what's already on disk rather than needing anything from the server or any new sync. ALIKEovermessagefiltered bychat_jidwould probably cover most of what people want, and FTS could come later if it's ever worth it.Alternatives considered
No response