Bug 20154

Summary: quiting more/less on the console early leav
Product: Base System Reporter: mwm
Component: binAssignee: Andrey A. Chernov <ache>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.0-CURRENT   
Hardware: Any   
OS: Any   

Description mwm 2000-07-24 19:50:01 UTC
	The sc console device is left in reverse video mode after a quit
	from less or more. This doesn't seem to happen with xterms.

Fix: 

Sorry, I don't have it :-(.
How-To-Repeat: 
	Log into an sc console, and try "more /etc/termcap". At the
	bottom of the first page, hit the "q" key. Notice that the
	last line is reverse video. Try "clear", and get a screen
	that's reverse video. To clear this, use "more /etc/motd" (or
	some short file) and page through to the end. You can then
	recreate the problem with a "less /etc/termcap" and quiting
	early. Less cannot be used to fix the problem.
Comment 1 Андрей Чернов 2000-07-24 20:14:10 UTC
On Mon, Jul 24, 2000 at 06:45:43PM -0000, mwm@mired.org wrote:
> >Environment:
> 
> 	Build on -current cvsupped July 21, 2000. Kernel from July 16, 2000.
> 	It's not clear when the problem appeared.

Kernel must be updates since syscons changed. Leaving old variant in
termcap is not possible, because the bug: all attributes turned off on
"se" instead of standout only.

-- 
Andrey A. Chernov
<ache@nagual.pp.ru>
http://ache.pp.ru/
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 2000-11-27 09:23:58 UTC
State Changed
From-To: open->feedback

Mike, could you confirm that this isn't a problem in today's 
CURRENT with an up-to-date termcap database?  I can't 
reproduce the problem here.
Comment 3 mwm 2000-11-27 13:39:01 UTC
sheldonh@FreeBSD.org types:
> Synopsis: quiting more/less on the console early leav
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: sheldonh
> State-Changed-When: Mon Nov 27 01:23:58 PST 2000
> State-Changed-Why: 
> Mike, could you confirm that this isn't a problem in today's
> CURRENT with an up-to-date termcap database?  I can't
> reproduce the problem here.

Yes, this is no longer a problem. Andrey nailed it, and as soon as I
got the kernel & userland back in sync, the problem went away.

	Thanx,
	<mike
Comment 4 Sheldon Hearn freebsd_committer freebsd_triage 2000-11-27 13:40:48 UTC
State Changed
From-To: feedback->closed

Andrey's analysis was spot on. 


Comment 5 Sheldon Hearn freebsd_committer freebsd_triage 2000-11-27 13:40:48 UTC
Responsible Changed
From-To: freebsd-bugs->ache

Andrey's call.