From owner-freebsd-questions Sun Nov 21 16:36:59 1999 Delivered-To: freebsd-questions@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id EF9711510C for ; Sun, 21 Nov 1999 16:36:53 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from sasknow.com (ntstn [10.0.0.2]) by sasknow.com (8.9.3/8.9.3) with ESMTP id SAA15871; Sun, 21 Nov 1999 18:37:21 -0600 (CST) (envelope-from freebsd@sasknow.com) Message-ID: <383890FB.67D65021@sasknow.com> Date: Sun, 21 Nov 1999 18:40:27 -0600 From: "Ryan Thompson [FreeBSD]" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Guillaume Paquet Cc: freebsd-questions@FreeBSD.ORG Subject: Re: prompt and default editor References: <001e01bf345b$722ec800$0201a8c0@cgocable.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Guillaume Paquet wrote: > > Hi, > > 1) How can I change my prompt? like myhostname@pwd$ > > I'd like to have an example please. I use something like the following in my .cshrc: set prompt=`whoami`@`hostname`:$cwd Then, to keep the path current, you'll need to add something like: alias cd 'cd \!* ; set prompt=`whoami`@`hostname`:$cwd"$ "' alias pushd 'cd \!* ; set prompt=`whoami`@`hostname`:$cwd"$ "' alias popd 'cd \!* ; set prompt=`whoami`@`hostname`:$cwd"$ "' For example, you might see: foub@globetrotter.net:/home/foub $ _ Of course, if your terminal can do colour, it's often nice to colorize your prompt so that you can pick it out at the end of a directory listing or long output. Find an ANSI color code reference to do this. Such frivolity is beyond the scope of this message :-) > 2) How can I change the default editor of quota\crontab? vi --> pico setenv EDITOR /usr/local/bin/pico .. Should do the trick for "most" applications. If not, you can always use: alias vi /usr/local/bin/pico .. But I would really recommend keeping vi functional, in case you (or someone else) needs it. If that STILL doesn't work, then the application in question uses a fully qualified path to access vi. (That, or you didn't reload your .cshrc/relogin after making the changes :-) Look for configuration files or header files. Hope this helps. Virtually yours, - Ryan -- Ryan Thompson VP Technical/Accounts ryan@sasknow.com (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th Street East Saskatoon, Sask S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message