Re: Purpose of jde-autoloads

Przemysław Wojnowski <[email protected]> writes:

> The only function I would 
> see in autoloads would be something like this:
> (defun jde-start ()
>    "Start JDEE."
>   (require 'jde))
>
> Rationale: If someone would install JDEE (e.g. from elpa) it wouldn't slow down 
> Emacs startup. But user could load it anytime using M-x jde-start when s/he 
> would like to open a Java project.

I have another problem with this; it's backward incompatible. We'll get
lots of (well, some :) complaints "why doesn't JDE work anymore"?

It's also not the way Emacs packages are expected to work. Once you
install an ELPA package, it should be transparent; open a java file,
and JDE is there. We don't want users wondering;

    "Why isn't this jde command working? Oh, right, I forgot 'jde-start'".

The minimum set of autoloaded commands is the set that are likely to be
the first JDE command people use. That's at least jde-mode, and probably
a few others (I haven't used it enough yet to tell).

Additional autoloads can be used to reduce the initial load time. As you
rightly point out, the need for that is less these days than it used to
be.

But the commandment "don't 'fix' what isn't broken" is still a good one,
here.

-- 
-- Stephe

------------------------------------------------------------------------------
_______________________________________________
jdee-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jdee-devel