NetBSD Problem Report #9152

Received: (qmail 14364 invoked from network); 9 Jan 2000 15:34:31 -0000
Message-Id: <200001091517.JAA21172@rkr.kcnet.com>
Date: Sun, 9 Jan 2000 09:17:52 -0600 (CST)
From: Richard Rauch <rauch@math.rice.edu>
Reply-To: rkr@olib.org
To: gnats-bugs@gnats.netbsd.org
Subject: window(1) problems.
X-Send-Pr-Version: 3.95

>Number:         9152
>Category:       bin
>Synopsis:       window(1) has odd behavior.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 09 07:36:00 +0000 2000
>Closed-Date:    
>Last-Modified:  Tue Aug 02 03:07:50 +0000 2011
>Originator:     Richard Rauch
>Release:        1.4.1
>Organization:
  "I probably don't know what I'm talking about."  --rkr@rkr.kcnet.com
>Environment:

System: NetBSD rkr.kcnet.com 1.4.1 NetBSD 1.4.1 (olibGENERIC) #3: Tue Nov 30 01:09:25 CST 1999 root@rkr.kcnet.com:/usr/src/sys/arch/i386/compile/olibGENERIC i386


>Description:
    Recently, my regular monitor died.  The stand-in doesn't seem to like
    my X configuration, but I can use it for text consoles.  So, with good
    reason, I returned to good ol' window(1).  Several problems ensued.

     * Support for cursor keys in place of h/j/k/l would be nice.  Likewise,
       support for page-up/page-down (where available) in place of
       K/J (respectively)
     * PINE and PICO think that they know how to use the window, but
       single-character inserts do not seem to work correctly.  Visually,
       they act like overstrike mode.
     * PC page-up/page-down keys seem to cause problems.  Lynx knows
       how to handle them through window; PINE does not.  Both work
       flawlessly with a direct wscons console.
     * There may be a good reason for it, but because vt100 emulation
       is essentially non-existant under window, you cannot readily
       masquerade as a vt100 when accessing remote systems.  (This would
       be useful, since there is no regular termcap entry for window, and
       while su/ssh export TERM, they do not export TERMCAP env variables.)
       (That TERMCAP isn't exported is probably a bug in those programs,
        but by using a TERMCAP-resident termcap entry, rather than one
        in a termcap file, and apparently using an idiosyncratic terminal
        protocol, it is hardly robust against terminal-config problems.)

    Some problems may be i386- or wscons-specific.
>How-To-Repeat:
	Start window.
	Spend a little while trying to make window your home (use
	``su -l'' once, even; telnet/ssh to another host (or the same host)
	from a window console...).
	Try using PINE locally under window.
>Fix:
	No actual fix is offered at the moment.  But some workarounds worth
	noting:

	screen exists in the packages.  I may give screen a try to see if
	it cures some of my problems---but since window is what ships with
	NetBSD, it should probably be fixed.

	ssh claims to support an /etc/environment file for exporting further
	environment variables.  I can't see that it works, however.

	You can manually forward TERMCAP settings by opening a new window,
	finding the current TERMCAP settings, and pasting them appropriately
	into the telnet/ssh/su/whatever window.

	PINE and PICO seem to insert correctly if you strike the keys fast
	Enough---and you can always use ^L to refresh.

	SOMETHING is being sent for pageup/pagedown on the i386 wscons.
	Lynx knows what to do with it, but precious little else does.
>Release-Note:
>Audit-Trail:
Changed From: header on submitter's request from
Richard Rauch <rkr@rkr.kcnet.com>
to <rauch@eecs.ku.edu>
[wiz 2001-06-09]
Changed From: on submitter's request. [wiz 2001-07-11]
State-Changed-From-To: open->suspended
State-Changed-By: jruoho@NetBSD.org
State-Changed-When: Tue, 03 May 2011 14:14:19 +0000
State-Changed-Why:

Suspended as window(1) is going to be removed after 6.0.



State-Changed-From-To: suspended->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 17 Jul 2011 03:04:41 +0000
State-Changed-Why:
no point suspending this; it is a clear WONTFIX. :-/


From: Julio Merino <jmmv@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc: dholland@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, 
 rkr@olib.org
Subject: Re: bin/9152 (window(1) has odd behavior.)
Date: Mon, 01 Aug 2011 22:55:43 -0400

 On 7/16/11 11:04 PM, dholland@NetBSD.org wrote:
 > Synopsis: window(1) has odd behavior.
 > 
 > State-Changed-From-To: suspended->closed
 > State-Changed-By: dholland@NetBSD.org
 > State-Changed-When: Sun, 17 Jul 2011 03:04:41 +0000
 > State-Changed-Why:
 > no point suspending this; it is a clear WONTFIX. :-/

 The code will continue to be available in othersrc and installable
 through pkgsrc, so I believe this has to be reopened.

 -- 
 Julio Merino / @jmmv

State-Changed-From-To: closed->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Tue, 02 Aug 2011 03:07:50 +0000
State-Changed-Why:
reopen by request.


>Unformatted:

Home	PR Database Search