emacs-for-vimmers VS melpa

git clone https://github.com/ideasman42/emacs-for-vimmers

Suggest to start off with a small vim-like config if doom or spacemacs aren't for you (see emacs-for-vimmers).

I prefer not to depend on any existing frameworks, here is the emacs/VIM config I wish I had starting out - minimal & commented: emacs-for-vimmers

If you don't want a starter kit - but are interested in a commented vim-like setup, checout: emacs-for-vimmers. Even if you are not into VIM, the defaults may be of interest to you.

I came from a fairly similar place, this is a fairly minimal package set to have a useful evil-mode up and running: https://github.com/ideasman42/emacs-for-vimmers

This is a fully self contained config made by making minor changes to emacs-for-vimmers that works in my tests.

If you'd like to have a reference for a lite weight vim/emacs setup, checkout https://github.com/ideasman42/emacs-for-vimmers - for a commented configuration that gets you up and running without having to buy into a framework.

Suggest https://github.com/ideasman42/emacs-for-vimmers to get you up and running with something approximating a typical development configuration in VIM.

Check packages used by emacs-for-vimmers - the config file is short and commented, giving a minimal VIM-like setup that includes features useful to developers.

If you like building your own config from scratch - check out emacs-for-vimmers as a reference.

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.