- Subject: Re: Disable jed.conf (was: Re: Intention of jed-script)
- From: "G. Milde" <g.milde@xxxxxx>
- Date: Mon, 11 Jul 2005 11:54:11 +0200
On 8.07.05, Joerg Sommer wrote:
> "John E. Davis" <davis@xxxxxxxxxxxxx> wrote:
> > Joerg Sommer <joerg@xxxxxxxxxxxx> wrote:
> >>If yes, I think it should not load site.sl, because there are not options
> >>to tell jed-script to not load user config, which leads to bizarre
> >>effects.
> >
> > jed-script does not load your .jedrc file.
>
> Then site.sl is my problem:
I'd say the problem is not site.sl but jed.conf (and the files loaded from
it).
> I think it is really necessary to _not_ load jed.conf some times. One
> time is when jed is called as jed-script and the other situation when a
> command line option is given, e.g. --no-etc-conf. How do you think?
I'd call this option --no-jed-conf or --no-conf, as it should disable
defaults.sl as well.
> The problem I observed, if root has a directory ~/.jed/lib/dfa and
> jed.conf runs home-lib.sl, the dfa files will be created in this
> directory and not in JED_ROOT/lib.
This is actually actually bug in home-lib.sl. I should probably change the
Jed_Highlight_Cache_Dir only if the current setting is not writable (so
the average user can store newly created dfa files).
Günter
--
G.Milde web.de
[2005 date index]
[2005 thread index]
[Thread Prev] [Thread Next]
[Date Prev] [Date Next]