Date: Mon, 19 Feb 1996 10:27:04 +0100 (MET) From: schweikh@ito.uni-stuttgart.de (Jens Schweikhardt) To: FreeBSD-gnats-submit@freebsd.org Subject: bin/1035: ls does not show unprintable chars (change request) Message-ID: <9602190927.AA00773@itosun.ito.uni-stuttgart.de> Resent-Message-ID: <199602190930.BAA14136@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1035 >Category: bin >Synopsis: ls to terminal always uses ? for non-printable chars >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Feb 19 01:30:02 PST 1996 >Last-Modified: >Originator: Jens Schweikhardt >Organization: Uni Stuttgart >Release: FreeBSD 2.1-STABLE i386 >Environment: >Description: According to the ls(1) man page, non-printable characters in filenames are displayed as ? by default if output is to a terminal. There is the -q option to force this even when output is to a file. However, force printing non-printable characters is impossible when output is to a terminal. Or can this behaviour be changed using locale settings? The man page ls(1) does not say anything about it. And I remember having set locales and getting core dumps from xterm... >How-To-Repeat: Create a file with an a-umlaut in the name. Say ls. Suggested fix: add new option that prints filename as is, no matter what it is and where output goes. (although I'd rather see the default behaviour changed, and make the -q option not depending on isatty(stdout)). Bye, Jens >Fix: >Audit-Trail: >Unformatted: To: FreeBSD-gnats-submit@freebsd.org Subject: ls to terminal always uses ? for non-printable chars From: schweikh@ito.uni-stuttgart.de Reply-To: schweikh@ito.uni-stuttgart.de X-send-pr-version: 3.2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9602190927.AA00773>