jed_add_feature

[g.milde@xxxxxx]

Hi,

I am taking up an issue discussed almost one year ago...

On Fri, 11 Apr 2003 14:31:38 -0400 wrote "John E. Davis" <davis@xxxxxxxxxxxxx>:

> Perhaps a reasonable compromise would be to have a list of features to
> be loaded at startup after loading the personal .jedrc file, with a
> mechanism to modify that list before the loading takes place.  For
> example,
> 
>    % code in site.sl
     ...  
           
>    % load jedrc startup file code
>       .
>       .
>    % Now load features
>      foreach (Default_Feature_List) using ("keys")
>        {
>           feature = ();
>           require (feature);
>        }
> 
> Then, suppose that someone does not like the "recent" files feature.
> That that person's .jedrc file could contain
> 
>    jed_remove_feature ("recent");


Now, the Debian jed-extra package has exactly the problem
of "overridable" default activation of features.

My proposed solution is a variant of Johns example using the
_jed_startup_hooks (as we do not want to fiddle in site.sl).

However, to have it compatible, it would be nice to know:

Are there plans to implement this idea in the next release?

In this case, jed-extra could just contain an interim and rely on
jed_add_feature() for subsequent versions of Jed.

To get it compatible, the second question is:

Is there a change to the API (i.e. the function names)?


sincerely

Günter

-- 
G.Milde at web.de

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.