From: Dan Callaghan <dan@bl2.djc.id.au>
To: sup-commits@supmua.dev
Subject: [sup.git] 01/02: fix ambiguous / warning in new emit_xterm_title method
Date: Sun, 11 Oct 2026 08:23:33 +1100 [thread overview]
Message-ID: <20261010212332.B2C73296275@bl2.djc.id.au> (raw)
In-Reply-To: <179166741234.335316.11439183706167653222@bl2.djc.id.au>
New commit on branch develop:
https://supmua.dev/git/sup/commit/0d6a14bced9838695575c1e112dc3ecbfb299c8c.html
commit 0d6a14bced9838695575c1e112dc3ecbfb299c8c
Author: Dan Callaghan <djc@djc.id.au>
AuthorDate: Sat Oct 10 18:08:03 2026 +1100
fix ambiguous / warning in new emit_xterm_title method
lib/sup/buffer.rb:301: warning: ambiguous `/`; wrap regexp in parentheses or add a space after `/` operator
---
lib/sup/buffer.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
index 7561d54d..75becf24 100644
--- a/lib/sup/buffer.rb
+++ b/lib/sup/buffer.rb
@@ -298,7 +298,7 @@ EOS
## Screen does not properly handle characters above U+FF in the title.
## It truncates them to 8 bits which may cause it to emit control
## characters into the terminal title.
- title = title.gsub /[^\u0000-\u00ff]/, "?" if ENV["TERM"] =~ /screen/
+ title = title.gsub(/[^\u0000-\u00ff]/, "?") if ENV["TERM"] =~ /screen/
print "\033]0;#{title}\07"
end
next prev parent 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 [sup.git] branch develop updated (a17638d3 -> cf3a2e38) Dan Callaghan
2026-10-10 21:23 ` Dan Callaghan [this message]
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=20261010212332.B2C73296275@bl2.djc.id.au \
--to=dan@bl2.djc.id.au \
--cc=djc@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