From: Dan Callaghan <dan@bl2.djc.id.au>
To: sup-commits@supmua.dev
Subject: [sup.git] branch develop updated (a17638d3 -> cf3a2e38)
Date: Sun, 11 Oct 2026 08:23:32 +1100 [thread overview]
Message-ID: <179166741234.335316.11439183706167653222@bl2.djc.id.au> (raw)
Pushed branch develop:
from a17638d3 tests: fix TestLineCursorMode failures due to Ncurses.tigetflag
new 0d6a14bc fix ambiguous / warning in new emit_xterm_title method
new cf3a2e38 rewrite ThreadIndexMode#multi_kill to work like the other label methods
Summary of changes:
lib/sup/buffer.rb | 2 +-
lib/sup/modes/thread_index_mode.rb | 55 +++++++++++++++++++-------------------
2 files changed, 29 insertions(+), 28 deletions(-)
next reply other threads:[~2026-10-10 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 21:23 Dan Callaghan [this message]
2026-10-10 21:23 ` [sup.git] 01/02: fix ambiguous / warning in new emit_xterm_title method Dan Callaghan
2026-10-10 21:23 ` [sup.git] 02/02: rewrite ThreadIndexMode#multi_kill to work like the other label methods Dan Callaghan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179166741234.335316.11439183706167653222@bl2.djc.id.au \
--to=dan@bl2.djc.id.au \
--cc=sup-commits@supmua.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox