Hacker News new | comments | ask | show | jobs | submit login

Stefan's stewardship resulted in a much-improved Emacs. He did a very good job.

I'm really sorry to see Stefan go. The rate at which Emacs improved while he was maintainer contrasts quite strongly with the stagnation of some years before (6 years from Emacs 21 to Emacs 22).

Infrastructure changed a lot. major emacs packages are now upgraded everyday (I use melpa "rolling release"), so different than the emacs distribution every x years. Not to reduce Stefan role in emacs quality and liveliness. Seeing the praise he received says a lot.

How does that work with long-running emacs processes?

I generally keep a daemonized emacs or two running the entire duration of my uptime. If package A depends on a certain behavior of package B (but doesn't eagerly load it), if I start emacs, load package A, wait some duration X, package B gets updated, then I load package B, will A break?

If so, is that a failure of A for not eagerly loading B, or a failure of the dependency system for not letting A declare that it wants a particular version of B, or something else?

Sorry, I have not really dived into package.el all that much and the documentation is somewhat fragmented since everybody customizes it the way they want.

I don't know much either, I had folder issues many times (package-v1 still loaded trying to open .emacs.d/elpa/package-v1/some-file even though package-v1 has been deleted and now only package-v2 is on disk.

I remember a few elisp level error after upgrades.

BTW, there is also MELPA Stable https://stable.melpa.org

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact