[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

When to use kernel-builtin line editor?

To: linux-utf8@xxxxxxxxxxxx
Subject: When to use kernel-builtin line editor?
From: Tomohiro KUBOTA <tkubota@xxxxxxxxxxx>
Date: Sat, 27 Jan 2001 11:39:42 +0900
Mail-reply-to: tkubota@xxxxxxxxxxx
Reply-to: linux-utf8@xxxxxxxxxxxx
Sender: owner-linux-utf8@xxxxxxxxxxxx
User-agent: Wanderlust/1.1.1 (Purple Rain) EMY/1.13.8 (Tastes differ) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI)

Hi,

I have a basic question.
When does a user have a chance to use kernel-builtin line editor?

I can imagine the following cases:
 - login prompt
 - getchar(), gets(), scanf(), and so on

I ask this because if we have little chance to use it,
we can choose not to support non-ASCII characters.
(Do someone use non-ASCII characters for username/password?)

---
Tomohiro KUBOTA <kubota@xxxxxxxxxx>
http://surfchem0.riken.go.jp/~kubota/
"Introduction to I18N"
http://www.debian.org/doc/manuals/intro-i18n/
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

Follow-Ups:
- Re: When to use kernel-builtin line editor?
  - From: Marcin 'Qrczak' Kowalczyk

Prev by Date: Re: X input methods for utf-8?
Next by Date: xterm-150-23-k5 patch
Previous by thread: Re: backspace, erase modes
Next by thread: Re: When to use kernel-builtin line editor?
Index(es):
- Date
- Thread