obvious.el
Who needs comments when the code is so obvious (by alphapapa)
package-lint
A linting library for elisp package metadata (by purcell)
obvious.el | package-lint | |
---|---|---|
4 | 6 | |
48 | 185 | |
- | - | |
2.4 | 7.7 | |
about 1 year ago | 8 days ago | |
Emacs Lisp | Emacs Lisp | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
obvious.el
Posts with mentions or reviews of obvious.el.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-06.
- obvious.el: Who needs comments when the code is so obvious
-
Example of simple mode that 'hides' superfluous text (e.g. XML)
This might be helpful: https://github.com/alphapapa/obvious.el
-
vanish.el: hide parts of a buffer
Cool. Another way to implement it, rather than using toggling commands, would be to use font-locking, which would improve performance in large buffers since it wouldn't be necessary to toggle the whole buffer at once. You can see how I did something similar here: https://github.com/alphapapa/obvious.el
- alphapapa/obvious.el: Who needs comments when the code is so obvious
package-lint
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
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.
What are some alternatives?
When comparing obvious.el and package-lint you can also consider the following projects:
dired-auto-readme - An Emacs package to automatically display a README file when one is present in a dired buffer.
compat - COMPATibility Library for Emacs Lisp
melpa - Recipes and build machinery for the biggest Emacs package repo
org-custom-cookies - An Emacs package that allows you to create custom cookies in org-mode
org-babel-hide-markers-mode - Hide/show source code blocks markers in Org-mode.
expand-region.el - Emacs extension to increase selected region by semantic units.
generators - Functions to generate data structures
org-view-mode - An attempt to create a markup-free read-only view mode for org-mode files in Emacs.
range-pattern - Range pattern for pcase
vanish.el - vanish.el: hide different parts of a buffer
obvious.el vs dired-auto-readme
package-lint vs compat
obvious.el vs melpa
package-lint vs org-custom-cookies
obvious.el vs org-babel-hide-markers-mode
package-lint vs dired-auto-readme
obvious.el vs expand-region.el
package-lint vs generators
obvious.el vs org-view-mode
package-lint vs range-pattern
package-lint vs vanish.el
package-lint vs org-babel-hide-markers-mode