Date: Tue, 11 Jun 1996 01:08:13 +0100 From: "Gary Palmer" <gpalmer@FreeBSD.ORG> To: Trencher <bradb@erinet.com> Cc: questions@FreeBSD.ORG Subject: Re: help with freebsd. Message-ID: <23754.834451693@palmer.demon.co.uk> In-Reply-To: Your message of "Sun, 09 Jun 1996 18:12:58 EDT." <31BB4C6A.2FDD@erinet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Trencher wrote in message ID
<31BB4C6A.2FDD@erinet.com>:
> well i have a suggestion. why not make the ls command in freebsd
> have a extra display to show if the file is executable or not.
> like maybe just a
> (filename)+(for being able to run it) then the rest ... .. ... . .. .
> (fileanme)-(can't be run) then the rest... .. .. .
> and maybe something for dirs like
> (dirname)> <-- that would mean it is a dir. the ` < '
> these would help a newbie greatly like ME!!!!!!
>From the `ls' man page:
-F Display a slash (/) immediately after each pathname that is a di-
rectory, an asterisk (*) after each that is executable, an at
sign (@) after each symbolic link, an equals sign (=) after each
socket, and a vertical bar (|) after each that is a FIFO.
One word of warning though. I copied my first ever .cshrc from someone
else, and those symbols appearing after the filenames confused the
h*ll out of me for a while (I couldn't understand why `ls' came up
with a file `foo*' but there was only a file `foo').
So that sort of thing could confuse more than help, unless explained
first in words of one sylable in big letters every time they logged
on...
Gary
--
Gary Palmer FreeBSD Core Team Member
FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23754.834451693>