[Pkg-jed-devel] jed-extra 1.0-1 in experimental

[G. Milde]

On 19.03.05, Rafael Laboissiere wrote:
 
> I just uploaded the jed-extra_1.0-1 package to the experimental
> distribution. 

Thanks. 
 
> It would be ideal to have these *.rc files integrated upstream in
> jedmodes.  Another possibility is to generalize the use of
> <INITIALIZATION> tags using make_ini.

This is the way I prefer (and I will use for my modes).

However, with make_ini() we could end up with way to many autoloads (if
no INITIALIZATION block is used, so trimming the modes would be needed in
this case too.

Generally, it should be possible to place the content of the *.rc files in
the <INITIALIZATION> block of the relevant files and collect them with
make_ini().

However, for most modes the automatic autoload feature of make_ini()
should suffice.


> You will also notice that a quite big amount of upstream files had to be
> patched in order to get the modes working correctly.  You will find the
> patches here:
> 
>     http://svn.debian.org/wsvn/pkg-jed/trunk/packages/jed-extra/patches/
> 
> I could volunteer to apply those patches directly to the CVS repository
> of jedmodes.sf.net and move then away from the Debian package.

Although (some of) the modes on Jedmodes are in a CVS repository, the policy
is not to fiddle with other peoples modes directly but to mail patches to
the author (see: http://jedmodes.sourceforge.net/doc/jedmodes-cvs.html).

I'll see what I can do for my modes:

ding:     added autoloads
gnuplot:  committed new version to CVS
          # what is the advantage of explicitely using info_find_dir?
ishell:   added autoload
view:     added require("keydefs")

BTW: most of the missing autoloads will be present in ini.sl, if you run
make_ini. 

This is also, why I frequently miss to insert them. I suppose I'll need a
way to disable the loading of ini.sl for testing purposes (something like
a check for the -n command line argument in home-lib.sl).

Guenter

-- 
G.Milde web.de