@bobfrankston/rmfmail 1.1.96 → 1.1.98

package/.commitmsg

@@ -1,15 +1,7 @@
-Alarm/snooze: log decisions to the daemon log so snooze is verifiable
+Signature now applied to replies/forwards, not just new mail
 
-On review the snooze keying is actually correct — snoozeItem stores under
-item.uuid, which IS the full per-occurrence key (uuid:startMs@offset for
-calendar, uuid:dueMs for tasks) that collectDueAlarms reads back as
-snoozed[key]. They match.
-
-What was missing was visibility: the [alarm] decisions used plain
-console.log, which from the WebView never reaches the daemon log file —
-so "is snooze working?" couldn't be answered after the fact. Added an
-alog() helper that mirrors to the daemon log via logClientEvent, a
-"snooze saved" line (key + minutes + untilMs), and routed the existing
-fire-decision / dismiss / unknown-result logs through it. Next snooze is
-now traceable: the "snooze saved" line and the following "fire decision"
-line confirm the snooze took and for how long.
+The new-format signature (acct.sig.text) was gated on "new mail only",
+so anyone using it got no signature on a reply or forward — only the
+legacy acct.signature field covered replies. Both formats now apply to
+new + reply + forward alike: above the quoted block on a reply/forward,
+at the end on new mail. Drafts still skip it (already in the saved body).

package/client/app.bundle.js

@@ -8647,8 +8647,11 @@ document.addEventListener("keydown", (e) => {
     applyFontSize(next);
   }
   if (e.ctrlKey && e.key === "a") {
+    const t = e.target;
+    const tag = t?.tagName;
+    if (tag === "INPUT" || tag === "TEXTAREA" || tag === "SELECT" || t?.isContentEditable) return;
     const mlBody = document.getElementById("ml-body");
-    if (mlBody && document.activeElement?.closest(".message-list, .ml-body, body")) {
+    if (mlBody) {
       e.preventDefault();
       mlBody.querySelectorAll(".ml-row").forEach((r) => r.classList.add("selected"));
     }