Hrvoje Niksic <hniksic(a)srce.hr> writes:
Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
> Hrvoje Niksic <hniksic(a)srce.hr> writes:
>
> > > The anology doesn't work as the loadpaths are computed before
> > > .emacs/init.el is loaded.
> >
> > The analogy definitely works. `.cshrc' is a special file, and can't
> > be placed just anywhere. It's not just a random executable. The same
> > goes for .emacs & friends.
>
> No it doesn't... The reason .cshrc is a special file in a special
> location is because there is no user dependent path setup in csh at
> the time it gets loaded.
No, that's not the reason, as I see it. The reason is that
.cshrc is
not *supposed* to be loaded from a random PATH location, ever.
It's potentially very dangerous to pull init files from miscellaneous
places. Has anyone else ever planted trojan .exrc files around to
catch^H^H^H^H^Heducate unwary vi users? :-)
$ cat .exrc
:!kill -11 $PPID