Bug#200857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200857

2003-07-14 Thread Thomas Dickey
   Debian Bug report logs - #200857
 xterm fails to honour dtterm sequence ESC[21t
...
   allowWindowOps (class AllowWindowOps)
   Specifies   whether   extended   windowcontrol
   sequences  (as  used  in  dtterm)  for  should  be
   allowed.
...
From: Vivek [EMAIL PROTECTED]
...
Ok then: assuming this defaults/will default to false, there's no
real need to stomp on the sequence handling completely, then, right?

That's my viewpoint - if Brendan adds a false to the system app-defaults
file, it would still allow a user to override it and get the features.

Making it return an empty string would be incorrect behavior - if it's
not implemented, it should be parsed  ignored.
-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#200857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200857

2003-07-14 Thread Thomas Dickey
   Debian Bug report logs - #200857
 xterm fails to honour dtterm sequence ESC[21t
...
   allowWindowOps (class AllowWindowOps)
   Specifies   whether   extended   windowcontrol
   sequences  (as  used  in  dtterm)  for  should  be
   allowed.
...
From: Vivek [EMAIL PROTECTED]
...
Ok then: assuming this defaults/will default to false, there's no
real need to stomp on the sequence handling completely, then, right?

That's my viewpoint - if Brendan adds a false to the system app-defaults
file, it would still allow a user to override it and get the features.

Making it return an empty string would be incorrect behavior - if it's
not implemented, it should be parsed  ignored.
-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net




Bug#200857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200857

2003-07-13 Thread Thomas Dickey
   Debian Bug report logs - #200857
 xterm fails to honour dtterm sequence ESC[21t
...

I think it might be better to do something like this [see patch]:
The iscntrl() test can be replaced easily if more/less paranoia is
required - it's not really fair to expect apps to figure out the
escape sequence is just gone, as afaict there's no way to ask if
a term supports many of them other than checking TERM and going by
what you know/expect that terminal to support.

not exactly - the label doesn't have control characters - see this chunk
in misc.c:

default:
if (ansi_table[CharOf(*cp)] != CASE_PRINT)
return;
}

The complaint is that someone could be misled into pressing return after
a bogus title was sent to the host, e.g., as part of cat'ing a core-dump
to the terminal.  (Why anyone would want to do this is another story).
Or doing tail -f on a so-called logfile (no different ;-).

This is in patch #174 (would allow someone to use these features if they're
inclined to read the manpage):

   allowWindowOps (class AllowWindowOps)
   Specifies   whether   extended   windowcontrol
   sequences  (as  used  in  dtterm)  for  should  be
   allowed.
-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#200857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200857

2003-07-13 Thread Thomas Dickey
   Debian Bug report logs - #200857
 xterm fails to honour dtterm sequence ESC[21t
...

I think it might be better to do something like this [see patch]:
The iscntrl() test can be replaced easily if more/less paranoia is
required - it's not really fair to expect apps to figure out the
escape sequence is just gone, as afaict there's no way to ask if
a term supports many of them other than checking TERM and going by
what you know/expect that terminal to support.

not exactly - the label doesn't have control characters - see this chunk
in misc.c:

default:
if (ansi_table[CharOf(*cp)] != CASE_PRINT)
return;
}

The complaint is that someone could be misled into pressing return after
a bogus title was sent to the host, e.g., as part of cat'ing a core-dump
to the terminal.  (Why anyone would want to do this is another story).
Or doing tail -f on a so-called logfile (no different ;-).

This is in patch #174 (would allow someone to use these features if they're
inclined to read the manpage):

   allowWindowOps (class AllowWindowOps)
   Specifies   whether   extended   windowcontrol
   sequences  (as  used  in  dtterm)  for  should  be
   allowed.
-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net