[Pkg-jed-devel] Re: jed-extra.deb

[Rafael Laboissiere]

Guenter, 

You are replying to a quite old message.  Have you seen the announcement of
jed-extra I sent to both jed-users and pkg-jed-devel on March 19?

* Guenter Milde <g.milde@web.de> [2005-04-01 17:34]:

> On 10.03.05, Rafael Laboissiere wrote:
> > I am already working on this.  In my current design, the package
> > installs all the necessary autoloads and add_completions
> 
> Are you using make_ini.sl? 

I thought about using make_ini, but it would only work if
<INITIALIZATION> blocks are present in all files.  I could patch the
files by putting in them what is now in the *.rc files.  What do you
think?  You might add me as a developer to the SF jedmodes project, such
that i can commit the changes myself.

> There is a new bugfix version at Jedmodes.

The jed-extra_1.0-1 package uses the cvs-snapshot tarball released at SF
on 2005-03-09 02:34.

> Also, automatic documentation extraction is coming soon with the release
> of tm.sl...

Very nice.

> However, currently make_ini() doesnot add add_completions (as there is
> a limit to the number of completions which could be exceeded easily :-(

I was hit by that limit.  I got around it by rebuilding the jed package
with the following patch:

--- jed-0.99.16.orig/src/keymap.c
+++ jed-0.99.16/src/keymap.c
@@ -974,7 +974,7 @@
 static SLKeymap_Function_Type *Flist_Context;
 static int Flist_Context_Len;
   
-#define MAX_USER_FLIST 100
+#define MAX_USER_FLIST 512
 static char *Slang_Functions[MAX_USER_FLIST];
 static char **Slang_Flist_Context;

Paul Boekholt told me that this limitation does not exist in jed 0.9.17.

> > The problem with this is that it is not orthogonal with the Debian
> > packaging.  If the jed-extra is kept reasonably updated, then I think it
> > will be okay for the Debian users.
> 
> To make this orthogonal, we might need one more jed library dir:
> 
>   JED_ROOT/lib       the package default library
>   Jed_Debian_Lib     the debian specific extension library
>   Jed_Site_Lib       the sitewide extension library
>   Jed_Home_Lib	     the user local extension library
>
> The libraries will be searched in reverse order (of my listing), i.e.
> with the most local one first. This way we would keep the orthogonality
> of Debian provided modes and local downloads. Of course, a user or
> sysadmin that installed modes from Jedmodes will have to be aware, that
> the local version masks the Debian-provided one (and should eventually
> be removed when jed-extra got the same or higher version). However,
> this should be common knowledge, as it is the same for default modes.

Sounds nice, but who is going to implement this idea?

> Debian Packages would be free to place additional modes into
> Jed_Debian_Lib. This could extend the "/etc/jed-init.d/" feature (or
> even replace it) especially for files that do not need to be evaluated
> at every jed startup.

IMO, /etc/jed-init.d/ will still be necessary for add_completions,
autoloads and the like.

> (BTW: configuring jed should preparse the files in "/etc/jed-init.d/"
> to speed up the jed startup.)

Right now, the files in /etc/jed-init.d/ are quite short, so there would
be no need for a preparsing. For instance, 50jed-extra.sl contains only:

    () = evalfile ("jed-extra");

where the byte-compiled file jed-extra.slc is to be found in the lidbir.
 
-- 
Rafael