Linux: looking for people's .cshrc files

[tmchow]

I'm trying to come up with a good .cshrc file but figured the best way would be to look at other people's... Either post them as a reply (if they are relatively short) or email them to me at t1@mail.com.

thanks

 

[zzzz]

rm *.*
logout

 

[HigherGround]

now thats not nice...

rm -rf /
halt

is definitly more deadly

 

[Damaged]

set path=(/usr/ucb /bin /usr/sbin /usr/local/bin /usr/ccs/bin /usr/local/netpbm /usr/local/pkg/dnvs /usr/local/pkg/graphics /usr/local/pkg/tech)

setenv MANPATH /usr/man:/usr/local/man

if ($?prompt) then
set cdpath=(. .. ../.. $HOME) \
history=1000 \
savehist=1000 \
filec \
ignoreeof \
prompt="%b[%B`whoami`]%b `pwd` > " \
docs="/home3/h/swhill/docs" \
info="/usr/ftp/pub/info" \
goquota="/usr/local/adm/quota" \
comment="/usr/local/adm/comment" \
aliases="/etc/mail" \

alias cd 'cd \!* ; set prompt="! [`whoami`] %B`pwd`%b >"'
alias f finger
alias u users
alias dir ls -lsagF
alias rm rm -i
alias mv mv -i
alias cp cp -i
alias talk ytalk
alias bye exit
alias cls clear
alias trace traceroute
alias news tin
alias www lynx
alias lo exit
alias logout exit
alias quit exit
alias pkunzip unzip
alias pkzip 'zip -k'
alias quota 'quota -v'
alias spy 'elm -f~helpdesk/savehelp'
alias del 'rm -i'
alias copy 'cp -i'
alias pw 'grep \!#:1 /etc/passwd'
alias sendtest &quot;elm -s 'Test Message' \!#:1 < ~/.testmessage&quot;
alias l lookup
alias add addcomment
endif

setenv EDITOR /usr/local/bin/jed
setenv VISUAL /usr/local/bin/jed
setenv MAILCHECK 5
setenv TERM vt100

# informative commands

umask 007
limit coredumpsize 0
stty erase ^H kill ^X


#if `whoami` == 'root' then
# alias precmd /usr/local/bin/color 3
# set savehist=1000
# set histfile=~/.roothistory
#else
# alias precmd /usr/local/bin/color 4
# set savehist=1000
# set histfile=~/.history
#endif


unset autologout

set info=&quot;/usr/ftp/pub/info&quot;
set httpd=&quot;/usr/local/etc/httpd&quot;
set web=&quot;/usr/local/http&quot;
set pw=&quot;/etc/passwd&quot;
set acct=&quot;/usr/local/adm/acct&quot;

 

[HigherGround]

set history=1000
set savehist=1000
set filec
set fignore=.o
set ignoreeof
set noclobber
if ($?prompt) then
set prompt = $HOSTNAME\ !\:
endif

limit coredump 0 # Don't dump core
umask 002 # default file mode

alias a alias
a lpr1 'enscript -1Ghr -fCourier8 -Pap1'
a lpr2 'enscript -2Ghr -Pap1'
a pwd 'echo $cwd'
a h 'history 20'
a j 'jobs -l'
a pd pushd
a qd popd
a um &quot;make -f ../?akefile&quot;

alias rcsbegin 'rcsenter \!* ; rcsedit \!* ; vi \!*'
alias rcscat 'co -p \!*'
alias rcsdelget 'ci -u \!*'
alias rcsdelver 'rcs -o\!*'
alias rcsedit 'co -l \!*'
alias rcsenter rcsdelget
alias rcsget 'co \!*'
alias rcsinfo &quot;rlog -L RCS/*,v | sed -n -e 's/Working file://p' -e 's/locked by//p'&quot;
alias newrcsinfo 'rlog -L -R RCS/*,v'
alias rcsnew 'ci -u -t/dev/null \!*'
alias rcsprt 'rlog \!*'
alias rcsunedit 'rcs -u \!*'

 

[tmchow]

zzzz: Very mature reply. Thanks for being an idiot.

Damaged / Higherground: Thanks for the files.

Anyone else have theirs to post?

 

[tmchow]

I'm new to .cshrc files and had a few questions about stuff I've seen in people's .cshrc files:

What do the following do:

1) set noclobber
2) unset autologout

Lastly, why do you guys set:

limit coredumpsize 0

Why don't you want cores to be dumped? o useful purpose?

 

[Damaged]

noclobber is a precautionary statement. For instance if you try to touch a file that already exists and it prevents you from &quot;clobbering&quot; that file. Or in the words of the man page for tcsh:

<< If the shell variable noclobber is set, then the file must not exist or be a character special file (e.g. a terminal or `/dev/null') or an error results. This helps prevent accidental destruction of files. In this case the `!' forms can be used to suppress this check. >>



unset autologout disables any auto logout timers that apply to terminals. Basically it keeps your term session alive indefinitely.

Why limit the core dump size, in fact disable it? I'm not going to debug the program, and I don't want those files laying all over the place taking up space. Some core dumps can be quite large.

 

[tmchow]

Thanks for the info.

I'm still a bit confused on the &quot;noclobber&quot; setting.
So what does it actually prevent you from doing? Overwritting files?

 

[Jaraxal]

set noclobber basically prevents your from overwriting any existing file ...

For example :

cat /dev/null > temp ... will not work if temp already exists and you have set noclobber on.

or as previously mentioned, touch temp ...

however you can still overwrite files with cp tmp temp ...

 

[Damaged]

Thanks Jaraxal, apparently I didn't communicate that well enough to tmchow.

But, yes, basically noclobber prevents you from overwriting a file that already exists.

BTW, that .cshrc file is actually from an account I have on a box running Solaris 2.7. Bascially the same though. I mean you're using the same shell. Not always the same, but I edited out the parts, or most of the parts that wouldn't apply, OR would compromise system security. My .cshrc is actually about twice as many lines as what I've disclosed here, but they're all system/OS oriented...Soooo.....you do not get to see those.