Mon, 30 Apr 2001 12:49:23 +0100, Simon Marlow <[EMAIL PROTECTED]> pisze:
> The problem is that both ~/.ghci and ./.ghci are useful: I use ~/.ghci
> to do things like :set +s, and define some useful macros. Whereas
> ./.ghci is great for doing things like:
>
>:set -iFoo:Bar
>:set -fglasgow-exts
>:load Main
You can implement your policies about ./.ghci in ~/.ghci by
:def readConfig \_ -> do doSomeChecks; readFile ".ghci"
:readConfig
For example enable ./.ghci as long as . is under $HOME.
But it's unsafe when somebody places Prelude.{o,hi} in .
(or IO.* or whatever modules doSomeChecks use).
And it's inconvenient to fit large expressions in a single line,
and local definitions share the namespace with code to be interpreted
interactively.
--
__("< Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
\__/
^^ SYGNATURA ZAST�PCZA
QRCZAK
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
