Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Nov 2010 20:45:11 GMT
From:      crocket <crockabiscuit@yahoo.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/152146: Virtual consoles ignore kb and kD termcap entries.
Message-ID:  <201011112045.oABKjBKg026384@www.freebsd.org>
Resent-Message-ID: <201011112050.oABKo8VE080030@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         152146
>Category:       misc
>Synopsis:       Virtual consoles ignore kb and kD termcap entries.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 11 20:50:07 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     crocket
>Release:        8.1-RELEASE
>Organization:
>Environment:
FreeBSD elisa.muffinplace.com 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
In cons25 termcap entry, kb=^H and kD=^?.
So I made cons25d entry and kb=\177 and kD=\E[3~ in cons25 in it.
cons25d entry inherits cons25 and overrides kb and kD.
After adding cons25d in /etc/termcap and logout and login,
the changes weren't applied.
After some inspection, I found out that csh is not aware of kb and kD.
It was obviously from the output of "telltc" builtin of csh.
I guess csh's ignorance of kb and kD caused the problem.

But xterm and genom-terminal covered for csh's ignorance of kb and kD.

Can FreeBSD virtual consoles be modified to deal with kb and kD even if a shell is not aware of it?
>How-To-Repeat:
Ctrl-v + backspace or del would print out the key symbols(^?, ^H, and etc)
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011112045.oABKjBKg026384>