package-lint
melpa
package-lint | melpa | |
---|---|---|
6 | 104 | |
185 | 2,687 | |
- | 0.9% | |
7.7 | 9.7 | |
8 days ago | 5 days ago | |
Emacs Lisp | Emacs Lisp | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
package-lint
-
Small elisp question
Exactly! This is also why I like Compat. I have to read through the Emacs NEWS anyway, then I can just as well add the functions directly to Compat. The small downside however is that Compat pretends that some function is available in your Emacs. If you write a package you must look twice where a function is coming from. This should not be a problem if you use package-lint, which you should! But see also https://github.com/purcell/package-lint/issues/227.
-
Compat 29.1.3.0
Thank you for reading that far. If you have feedback, questions or improvement proposals, please let me know. I hope that Compat is useful for you. If you miss some important functionality, feel free to open an issue on the issue tracker. Any help in adding missing functionality is welcome. In case you are interested in upstream development, you may want to help with scanning through years of the Emacs Git log for added functionality. A laborious process, but the Emacs library diffs from package-lint are useful. Unfortunately package-lint does not yet support Compat and warns if you use compatibility functions. Also package-lint does not yet track argument number changes. Help with those package-lint issues would be greatly appreciated.
-
Some of my plugins which will be published to MELPA
I would suggest using the checkdoc command in each of your package buffers. It will point out stylistic errors. flymake-mode will help catch byte-compilation errors as well. You should also install https://github.com/purcell/package-lint and M-x package-lint-current-buffer to get these up to par for MELPA.
-
org-custom-cookies: create custom statistics cookies in org-mode
(Note that the current minimum requirement for Emacs is set to 27.2, I'm pretty sure this can be lowered but I'm waiting on this issue for confirmation. Until then, if you have an older version, you should probably be able to install with quelpa just fine).
-
vanish.el: hide parts of a buffer
Also consider using checkdoc and package-lint before you publish stuff, it is really annoying to get warning pop-up for docs wider than 80 chars. Those are so easy to catch up. Generally, it is good to follow Melpa guidelines even if you don't plan to publish your package in Melpa.
-
[ANN]: fill-sentences-correctly.el: Fill sentences with two spaces after a period while accepting one
I strongly suggest you to use package-lint when writing packages. It will point out all version mismatches, and some other things.
melpa
-
Alternatives to reddit and r/emacs to stay updated on Emacs developments
Watch the new pull requests to melpa: https://github.com/melpa/melpa/pulls
- Ask HN: What's a good, privacy focused bookmark manager?
-
Can't remove Emacs as "cask emacs is not installed"
(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)))
-
Trying to understand the difference between GNU ELPA and NonGNU ELPA. Plz help.
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.
- What is your favorite IDE?
- New minimalistic dashboard.
-
is there like a resource where I can learn how to create an elisp project
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.
-
melpa.org blacklisted ?
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-fly-keys not on melpa?
Xah asked for his packages to be removed from MELPA a while back: https://github.com/melpa/melpa/issues/7755
-
Elisp project best practices
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.
What are some alternatives?
compat - COMPATibility Library for Emacs Lisp
straight.el - 🍀 Next-generation, purely functional package manager for the Emacs hacker.
org-custom-cookies - An Emacs package that allows you to create custom cookies in org-mode
elpa-mirror - Create local emacs package repository. 15 seconds to install 115 packages.
dired-auto-readme - An Emacs package to automatically display a README file when one is present in a dired buffer.
use-package - A use-package declaration for simplifying your .emacs
generators - Functions to generate data structures
nano-emacs - GNU Emacs / N Λ N O - Emacs made simple
obvious.el - Who needs comments when the code is so obvious
emacs-undo-fu
range-pattern - Range pattern for pcase
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]