package-lint

A linting library for elisp package metadata (by purcell)

Package-lint Alternatives

Similar projects and alternatives to package-lint

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better package-lint alternative or higher similarity.

package-lint reviews and mentions

Posts with mentions or reviews of package-lint. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-04.
  • Small elisp question
    2 projects | /r/emacs | 4 Feb 2023
    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
    6 projects | /r/emacs | 22 Jan 2023
    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
    4 projects | /r/emacs | 28 Dec 2022
    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
    3 projects | /r/emacs | 27 Sep 2022
    (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
    8 projects | /r/emacs | 6 Aug 2022
    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
    2 projects | /r/emacs | 30 Dec 2021
    I strongly suggest you to use package-lint when writing packages. It will point out all version mismatches, and some other things.
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 1 May 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic package-lint repo stats
6
185
7.7
about 1 month ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com