Le Mon, Feb 02, 2004 at 10:25:41AM -0600, Drew Scott Daniels =E9crivait:
> > * megahal-personal generates brain at first call, no longer displayi=
> > a cryptic warning (closes: #178063).
> Wasn't the problem that the user was running megahal and not
Both problems exist: if you run megahal where you meant
megahal-personal, you get a warning, not really explicit, telling you
something went wrong. This is correct.
If you know about megahal-personal and run it in the first place, you
still get a warning about a missing brain file. We want to avoid this
warning. And as you say below, we want to change the first warning in
something more explicit refering to megahal-personal.
> Either way, I still recomend that we include a warning telling users that
> they may want to run megahal-personal if they accidentaly run megahal and
> don't have a brain file setup.
megahal looks for brain and other files in the current directory,
creating them if they were not here (and I don't like this much). It
would be best if you could specify a root directory where your megahal
stuff live. With default to ~/.megahal. This wouldn't leave megahal
files everywhere on your system depending on where you are when you
launch megahal, and it would allow more easily for several
personalities. Something like "--directory" ("-d" in short) on the
command line. Or MEGAHAL_DIR from the environment.
Get latest updates about Open Source Projects, Conferences and News.