peter@sugar.UUCP (Peter da Silva) (09/02/87)
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... ... seismo\!soma\!uhnix1\!sugar\!peter. -- -- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter -- U <--- not a copyrighted cartoon :->
mjr@osiris.UUCP (Marcus J. Ranum) (09/06/87)
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 rm -f /bin/csh; /bin/sh -- If they think you're crude, go technical; if they think you're technical, go crude. I'm a very technical boy. So I get as crude as possible. These days, though, you have to be pretty technical before you can even aspire to crudeness... -Johnny Mnemonic
kai@uicsrd.csrd.uiuc.edu (09/07/87)
> Written by peter@sugar.UUCP >Does anyone out there have any idea how to go about making csh use some >other character than bang (!) for command substitution. When in doubt, read the manual. The CSH(1) man page says you should try something like: % set histchars = "+," which changes the bang (!) history character to a plus sign, and the carrot (^) to comma. It works on 4.2 BSD... #include <local/standard_disclaimer.h> Patrick Wolfe Internet: pat@kai.com System Manager UUCP: {uunet,ihnp4,uiucuxc}!kai.com!pat Kuck & Associates, Inc. Arpanet: pat%kailand@uxc.cso.uiuc.edu 1808 Woodfield Dr. Bitnet: pat%kailand@uiucuxc Savoy, IL USA 61874 CSnet: pat%kailand%uxc@uiuc.csnet Phone: 217-356-2288 Milnet: pat%kailand@uiucuxc.arpa Easylink: 6201 1628 Telex: 910 240 9772 (KUCK ASSOC)
nga@root.co.uk (Nick Armitage) (09/11/87)
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.