Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!ukc!stc!root44!nga
From: nga@root.co.uk (Nick Armitage)
Newsgroups: comp.misc
Subject: Re: Ban the bang!
Message-ID: <427@root44.co.uk>
Date: Fri, 11-Sep-87 03:59:23 EDT
Article-I.D.: root44.427
Posted: Fri Sep 11 03:59:23 1987
Date-Received: Sun, 13-Sep-87 09:14:33 EDT
References: <624@sugar.UUCP>
Organization: Root Computers Ltd., London, England
Lines: 36
Keywords: csh uucp conflict bang command_replacement
Summary: an answer..

In article <624@sugar.UUCP>, peter@sugar.UUCP (Peter da Silva) writes:
> Does anyone out there have any idea how to go about making csh use some
> other character than bang (!) for command substitution. Uucp and csh
> are uneasy partners...

to set you history character to a comma, you might include the
following line in your .cshrc or .login:

set histchars = \,^

i have found that the most popular alternative history characters locally
(please don't start a net debate on this one) are comma and underbar.
it really depends on 1) what is already used 2) if you can type it
unshifted on your keyboard.

the next line determines the length of your history, there is an internal
maximum which you cannot exceed:

set history =  100

if you are feeling particularly flash, you can change your prompt
to indicate which machine you are on and who you are logged in as:

set prompt = `hostname`!`whoami`"[\,]: "

btw, the thing inside the square brackets must be the history character
preceeded by a backslash if you want to get the command numbers.

hope this answers your question. sorry i couldn't email it, but our
backbone bounced it..

nick
-
Nick Armitage, Root Technical Systems, 3 Hayne Street, London, EC1A 9HH.
phone:  +44 1 606 7799   fax:  +44 1 726 8158   telex:  885995 ROOT G
My opinions do not necessarily represent those of any ROOT-Unisoft company.