From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] interface blinking and corrupted on the console
Date: Wed, 09 Jan 2008 08:09:48 -0800 [thread overview]
Message-ID: <1199894905-sup-3585@south> (raw)
In-Reply-To: <1199563333-sup-1769@tomsk>
Excerpts from Marcus Williams's message of Sat Jan 05 12:11:14 -0800 2008:
> I think checking if $TERM is one of "xterm.*" and "rxvt.*". I'd also
> add "screen" to the list as well (because screen deals with it and my
> main usage of sup is during a screen session :) and maybe "cyg.*" for
> whatever the cygwin term variable is (I think its cygwin but might be
> cygterm cant remember). Needs to be a regex because you get stuff
> like xterm-color.
Ok, I just committed this to git master:
commit 9722a770cadd44ddc4af6ddcb56eb8edb35c93b9
Author: William Morgan <wmorgan-sup at masanjin.net>
Date: Wed Jan 9 08:06:39 2008 -0800
only set terminal title if $TERM is an xterm or rxvt variant
diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
index fa1afe6..782695b 100644
--- a/lib/sup/buffer.rb
+++ b/lib/sup/buffer.rb
@@ -63,6 +63,7 @@ class Buffer
@title = opts[:title] || ""
@force_to_top = opts[:force_to_top] || false
@x, @y, @width, @height = 0, 0, width, height
+ @in_x = ENV["TERM"] =~ /(xterm|rxvt)/
end
def content_height; @height - 1; end
@@ -262,7 +263,7 @@ EOS
get_status_and_title @focus_buf # must be called outside of the ncurses
end
- print "\033]2;#{title}\07" if title
+ print "\033]2;#{title}\07" if title && @in_x
Ncurses.mutex.lock unless opts[:sync] == false
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-09 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 12:58 Giorgio Lando
2008-01-05 18:33 ` William Morgan
2008-01-05 20:11 ` Marcus Williams
2008-01-09 16:09 ` William Morgan [this message]
2008-01-09 17:49 ` Giorgio Lando
2008-01-09 18:09 ` William Morgan
2008-01-09 21:09 ` Marcus Williams
2008-01-09 23:02 ` William Morgan
2008-01-10 11:37 ` Marcus Williams
2008-01-05 21:32 ` Giorgio Lando
2008-01-05 22:01 ` Marcus Williams
2008-01-06 22:54 ` Giorgio Lando
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=1199894905-sup-3585@south \
--to=wmorgan-sup@masanjin.net \
/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