From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] interface blinking and corrupted on the console
Date: Sat, 05 Jan 2008 20:11:14 +0000 [thread overview]
Message-ID: <1199563333-sup-1769@tomsk> (raw)
In-Reply-To: <1199557847-sup-5728@south>
On 5.1.2008, William Morgan wrote:
> Does anyone know what the correct approach is for determining whether to
> set the title or not? Is it a matter of checking $TERM?
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.
Marcus
next prev parent reply other threads:[~2008-01-05 20:11 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 [this message]
2008-01-09 16:09 ` William Morgan
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=1199563333-sup-1769@tomsk \
--to=marcus-sup@bar-coded.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