update of jed-extra

[G. Milde]

On 11.07.05, Jörg Sommer wrote:
> G. Milde schrieb am Mon 11. Jul, 10:16 (+0200):
 
> > > I don't know how to find dfa cache files, whose name
> > > is set inside a SLang file.
> > 
> > This is a different problem, you could only grep in the SLang files.
> 
> This is ugly.

Do this at build time and provide a list? (In most cases, the name of *.sl
and *.dfa file coincide.)

Or create the dfa files at build time. (Are there problems with differnt
slang-versions also for dfa files?)


 
> > > > > > jed.conf should
> > > > > > 
> > > > > >   register_libdir(site-lib);
> > > > > >   % run the scripts in jed-init.d (might register more libraries)
> > > > > >   register_libdir(home-lib, local-lib);
> > > > > 
> > > > > But if a site admin decide to use a patched version of a file used in
> > > > > jed-init.d is version get not recognized. 
> > > > Do you mean: if a file in jed-init.d should use a file in local-lib or
> > > > home-lib instead of site-lib?
> > > Yes.
> > > 
> > > > Well, this is the prize we have to pay if we want packages to be able
> > > > to register their own libdirs. Otherwise this libdirs would take
> > > > precedence over local-lib and home-lib.
> > > 
> > > Why? If we register local-lib and home-lib in 30XX.sl it is still
> > > possible to register some mode, they can be overwritten in >30XX.sl
> > 
> > With this scheme, we had in jed-init.d
> > 
> >    00XX.sl        % files that might register package libraries
> >    ...
> >    29XX.sl
> >    30home-lib.sl  % register local-lib and home-lib
> >    31XX.sl        % files that can easily use modes from local-lib and
> >    ...            % home-lib but not register package libraries
> >    99XX.sl	  
> >    
> > I do not see the need for files >30XX.sl.
> 
> Me too, but 50jed-extra-init.sl and 55ispell.sl exists. :)

But they do not need access to local-lib or home-lib.

 
> > Debian packages should not need to use home-lib
> 
> I think we should support ~/.jed/. 

Of course support it, so the individual user has a place for extensions
and modifications. However, no Debian package should depend on the
existence of home-lib, while the order of jed-library-path will ensure
that all files are first searched for in home-lib.

> BTW: Why I need to place lib/ below ~/.jed/ for home-lib? I think it
> should be enought to have the lib stuff in .jed/.

~/.jed is the Jed_Home_Directory, 
   
   ...the user's so-called home directory where personal jed-related files
   are assumed to be found. 

This could include ~/.jed/doc, ~/.jed/.jedrecent, templates/, ...
In my ~/.jed, there are also jed-debian/ and jedmodes/ as well as
contribs/ and backup archives. I would not like to mix all this with
*.sl files.

OTOH, one could turn the tables and instead of 

  JED_ROOT
                            Jed_Site_Library
			    Jed_Local_Library
  Jed_Home_Directory        Jed_Home_Library

introduce
                            
  JED_ROOT               % standard
  Jed_Site_Directory     % new
  Jed_Local_Directory    % new
  Jed_Home_Directory	 % standard
  
where the corresponding libdir is always path_concat(..., "lib")

This would also solve the "where to place the docs" problem.

Günter


-- 
G.Milde web.de