[Pkg-jed-commit] r557 - jed-extra/trunk/debian/examples

[G. Milde]

On  6.02.07, Rafael Laboissiere wrote:
> Date: 2007-02-06 16:56:41 +0100 (Tue, 06 Feb 2007)
> New Revision: 557

> Modified:
>    jed-extra/trunk/debian/examples/50jed-extra.sl
> Log:
> Synched with jed-extra_2.2.1-1.etch.3
...

>  % Utilities (required by the other modes)
> -% append_libdir($1 + "utils/", 1);    % append and initialize
> +% append_libdir($1 + "utils/", 1);    % append and initialize
>  append_libdir($1 + "utils/", 0);  % append but do not initialize

What is the difference?
(almost all changes are invisible)


> -autoload("what_line_if_wide", "sl_utils");% needed by gdbmrecent.sl
> -autoload("buffer_dirname", "bufutils");   % needed by gdbmrecent.sl

Actually, I want these here in 50jed-extra.sl! I put them in again after
your decision to move them to 55jedstates.sl because I think they are
usefull for users of gdbmrecent (without jedstates package) and do no harm.

(The policy regarding this "manual autoloads" is, that all jed-extra modes
that are not in jed-extra/extra/ should work without additional autoloads
from the users side. As our first exchange about require("bufutils"), ...
vs. autoload() illustrates, this serves also a practical purpose.)

So, may I re-introduce the autoloads?

Günter