crux VS melpa

For those still on 28, crux-rename-file-and-buffer does the same thing (https://github.com/bbatsov/crux). I've been using it for half a decade at this point. This sort of command, that no other code will rely on, was never that important to get into core, and there's some merit in making people create the commands they needed. It's not like with the additions to subr and subr-x libraries (string-replace, string-search etc), which can't come fast enough.

Use vc-rename-file or crux-rename-file-and-buffer from crux

A similar functionality is in the crux package (see crux-delete-file-and-buffer).

How about https://github.com/bbatsov/crux?

Some packages I use for more effective text editing is crux for general text editing (video on crux), paredit for lisp editing and for org-mode:

I'll go with crux. It's not all about text editing, but it's got a lot of commands in dwim-fashion.

I learned the syntax of org-mode in an hour (maybe less), It has many superiorities to markdown (see this excellent essay). Emacs is a fully-featured tool, it's a lifetime of learning, just like all extremely powerful tools, you can see the blogs of many emacs experts like Bozhidar, Protesilaos, Karl Voit (to name a few) learning new features of Emacs quite regularly.

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.