From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] interface blinking and corrupted on the console
Date: Sat, 05 Jan 2008 10:33:14 -0800 [thread overview]
Message-ID: <1199557847-sup-5728@south> (raw)
In-Reply-To: <1199537691-sup-493@clarabella.clarabella>
Excerpts from Giorgio Lando's message of Sat Jan 05 04:58:50 -0800 2008:
> Hi, yet another issue. When I run sup on the plain console or on the
> framebuffer, it starts to beep and continues forever; everything
> blinks; keybindings seem to work (or at least I am able to get out with
> q).
I believe this is because of the way we're trying to set the X window
title. This patch should help temporarily:
--- cut here ---
diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
index fa1afe6..7f0ad81 100644
--- a/lib/sup/buffer.rb
+++ b/lib/sup/buffer.rb
@@ -262,7 +262,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
Ncurses.mutex.lock unless opts[:sync] == false
--- cut here ---
> This does not happen in X; also if I run sup into a screen session on
> the onsole everything works fine. Looking at my environment variables,
> the only thing which seems to distinguish the plain console from
> screen on the console is the TERM variable, which on the console is
> set to "linux". I have no similar issues with other ncurses apps on
> the console.
Does anyone know what the correct approach is for determining whether to
set the title or not? Is it a matter of checking $TERM?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-05 18:33 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 [this message]
2008-01-05 20:11 ` Marcus Williams
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=1199557847-sup-5728@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