[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: using use-package

From: Rusi
Subject: Re: using use-package
Date: Sun, 9 Aug 2015 10:03:34 -0700 (PDT)
User-agent: G2/1.0

On Sunday, August 9, 2015 at 10:15:33 PM UTC+5:30, Stefan Monnier wrote:
> > One basic property of FP is that things should not be more order sensitive
> > than the minimum (data-dependency) required
> Agreed.
> > By not having package-archive as an autoload, those two statements become
> > more order dependent than they (seemingly) need be.
> I don't see it that way: add-to-list is inherently different from setq
> (from a data-dependency point of view), so you can't expect
> (add-to-list 'foo bar) to work properly without first loading the
> package that defines foo.

Ok -- add-to-list uses foo as lvalue and rvalue so yes.

> Relying on variables being autoloaded would just open another can of worms.

This makes no sense
Either you (devs) deal with the worms.
Or we users.
If first the autoloads etc magic should be so cleverly arranged that (for 
 (setq foo-variable t)
 (foo-mode 1) 
and much more just works non-functional sequence of requires etc fudging

If second somebody or other will come up with use-package, req-package 
etc. We suffer the babel; you suffer its backlash

> > And if core emacs functionality can be thus fragile is it realistic to 
> > expect
> > random packages to satisfy all the new/changing/confusing best practices?
> AFAIK those "best practices" aren't very new and changing.  They've been
> used for bundled Emacs packages for many years and all GNU ELPA packages
> have strived to do the same from the very beginning.

Emacs predates the cloud era
Today with package archives the in thing, dependency management is inevitable
Do emacs packages have the sophisticated .deb style packaging?
My impression is that wheel will slowly and painfully and inevitably get 
Why not leapfrog?
> > IOW you folks should give a serious consideration to putting
> > (something like) use-package (better req-package) in the core
> The problem is to define "something like".

Simply solved -- Just pick up req-package :-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]