Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 43383

Summary: as of RedHat 7.0, tcsh doesn't accept meta chars; "nokanji" should be set by default
Product: [Retired] Red Hat Linux Reporter: Jonathan Kamens <h1k6zn2m>
Component: tcshAssignee: Eido Inoue <havill>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-06-28 14:57:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Kamens 2001-06-04 17:29:57 UTC 
Tcsh's KANJI feature was enabled in tcsh-6.09-6, which was included with
RedHat 7.0.  As a result, as of RedHat 7.0 or later, it's no longer
possible to create key bindings to meta characters (e.g., \377 for
backward-delete-word).

Given that this is a regression in functionality, and that the majority
majority of people will never use tcsh's kanji support, I think that this
support should be disabled by default, e.g., by putting "set nokanji" in
one of the files in /etc/profile.
Comment 1 Eido Inoue 2001-07-24 04:40:23 UTC 
KANJI enabling has been removed until a move I18N solution can be found.