Skip to content

OmaQ 1.1.2: keep local file paths out of recall and edits - #63

Merged
HANCORE-linux merged 2 commits into
mainfrom
fix/cli-recall-attachments
Oct 11, 2026
Merged

HANCORE-linux merged 2 commits into
mainfrom
fix/cli-recall-attachments

Conversation

@HANCORE-linux

Copy link
Copy Markdown
Owner

OmaQ 1.1.2 keeps the local path of a sent file or image out of outgoing messages. The helper and its protocol are unchanged (Protocol 16).

Changes

  • Recall in omaq-connect: Up/Down recalled the display text of sent file and image items, [file] <local path>, and Enter sent it as a chat message. Messages now carry their kind, and recall offers only text messages.
  • E in the bar: the keyboard shortcut started an edit on an own file or image item and put its local path into the composer, where Enter passes it to message.edit. E now follows the Edit button, which is already hidden for those items. The PlainText gate's two ChatPage source hashes are updated for this one-condition change.
  • Release metadata: manifest 1.1.2, docs/CURRENT.md, the user guide and the terminal-client stage.

Verification

  • make test, including the terminal client's 110 unit tests. The new recall test fails on v1.1.1 and passes here.
  • tests/chat-input-scroll.sh presses E on an own file item and an own image item in the real ChatPage, then on an own text message as the control, in direct and group chats. It fails on v1.1.1 (E edited an own file item) and passes here.
  • make helper, make arch and ./tests/no-signal-build.sh.
  • ./tests/phase2.sh and ./tests/phase8.sh.
  • qmllint ChatSurface.qml pages/ChatPage.qml Service.qml, omarchy plugin validate ., git diff --check and shellcheck on all *.sh.
  • A live test between two machines over the Tox network, with the real identities and this client on both sides:
    • after an own file transfer, Up offered the last text message on both sides, also after a restart reloaded the history, and Enter delivered only that text;
    • as controls, the installed 1.1.0 and 1.1.1 clients offered [file] <local path> on Up; the draft was cleared without sending;
    • neither machine's stored history contains a path of the other machine.

Up in omaq-connect recalled the display text of sent file and image
items, "[file] <local path>", and Enter sent it as a chat message.
Messages now carry their kind, and recall offers only text messages.

In the bar, E started an edit on an own file or image item and put its
local path into the composer. It now follows the Edit button, which is
already hidden for those items. The PlainText gate pins the new
ChatPage source hashes.
The manifest moves to 1.1.2, still Protocol 16. CURRENT.md and the
terminal-client stage name 1.1.2 for the recall fix, and CURRENT.md
says that editing applies to text messages.
@HANCORE-linux
HANCORE-linux merged commit 8dc83f3 into main Oct 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant