elegant-emacs VS melpa

Indeed!

I remember liking "elegance" at the time[0] by the same author.

[0]: https://github.com/rougier/elegant-emacs

E.g. https://github.com/rougier/elegant-emacs

If you want to try out some third-party packages in the beginning, I think the most "bang-for-your-buck" you'll get is with Avy. Also, expand-region. And specifically for writing: olivetti-mode, flyspell, dictionary, and Nicolas Rougier's Nano and Elegant Emacs setups.

I’m flattered by the attention—and I hope this ends up being genuinely useful for some people—but I would be remiss to not emphasize the tremendous work done by Nicolas P. Rougier on elegant-emacs.

Hi all, I've been working on bespoke-themes, which started out as a fork of Nicolas Rougier’s amazing work on elegant-emacs and nano-emacs. It sports a similar vibe, though some of the base colors are different and it is slightly less minimal and "opinionated" than nano-emacs. It also has the benefit of being (I hope) easily incorporated into one's existing emacs as a theme, rather than the more "distro" style of nano-emacs (which is a great project, but maybe not for everyone). I'm hoping to submit it to MELPA before too long. Long story short though, I'm looking for advice on the following:

`git pull https://github.com/rougier/elegant-emacs.git`, which will create a folder called elegant-emacs with the contents of the git directory wherever you call it.

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.