.emacs.d VS melpa

After a month or so, if you're still curious, try https://emacsrocks.com/

17 small length video tutorials of great quality (as informative as fun)

https://emacsrocks.com has lots of quick/digestable demos. This one is a favourite https://emacsrocks.com/e13.html (the ending is great, stick with it).

If anyone's looking for short demos, the https://emacsrocks.com shorts are great. My all-time favorite is https://emacsrocks.com/e13.html (well worth watching the ending).

Emacs Rocks! - A bunch of cool short videos that showcase cool tips and tricks.

We will mainly look at 3 packages: s.el, f.el and dash.el. Two of these packages (first and last) are maintained by Magnar Sveen, who are also known for Emacs Rocks and What The .emacs.d (which are still great resources for learning and finding inspiration for your Emacs configuration!). We will also look at ht.el. These packages are used a lot in many of the Emacs packages you use in a day to day basis, like lsp-mode and rustic just to name a few. As most of these already have tons of examples in their READMEs, my main goal of this article is to inspire you to check them out. Hopefully you will know of one new package after reading this article :)

Emacs Rocks!

Maybe you've seen them already but there's also http://emacsrocks.com/ videos, emacsconf too

Watch the new pull requests to melpa: https://github.com/melpa/melpa/pulls

(require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t) (package-initialize) (package-install 'use-package) (use-package exec-path-from-shell :ensure t :config (exec-path-from-shell-initialize)))

MELPA is definitely the biggest package archive, probably mostly on account of the lower barrier to entry compared to GNU ELPA (maybe the difference would have been less pronounced if NonGNU ELPA had been there from the beginning, but one can only speculate). MELPA has its own requirements for packages, but indeed copyright assignment to the FSF is not one of them.

I would suggest to start at reading the manual first. Then I would recommend reading the Melpa guidance, even if you do not plan to contribute your package to Melpa, since it contains very useful info about linting, writing your code etc.

The mxtoolbox link checks for SMTP blacklisting.. People won't be able to send mail from host with the IP address 178.128.185.1(which is the melpa.org webserver, not their mailserver, so everything's fine there).

Xah asked for his packages to be removed from MELPA a while back: https://github.com/melpa/melpa/issues/7755

Observe that package.el compile files when they are installed, and they are not compiled in any particular order (actually whatever directory-files returns, which is what OS returns). So if you have multiple files that depend on each other, it is something to think of. There are also some guidelines on how to structure your project on Melpa.