package-lint
A linting library for elisp package metadata (by purcell)
org-view-mode
An attempt to create a markup-free read-only view mode for org-mode files in Emacs. (by amno1)
package-lint | org-view-mode | |
---|---|---|
6 | 13 | |
189 | 46 | |
- | - | |
7.6 | 4.8 | |
19 days ago | 4 months 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.
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.
org-view-mode
Posts with mentions or reviews of org-view-mode.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-27.
-
Best looking org-modes you ever saw?
See if org-view-mode has something you can (re)use. It is not so much about styling aside from some quotes, and centered headlines, but more about removing unnecessary noise. See if it inspires or helps, it is relatively small and hopefully simple code.
-
Is there a lightweight syntax for writing code blocks in org-mode file?
For the clutter, you can try hiding src blocks or if you prefer hide all markup.
-
What are the kinds of things you've written Emacs Lisp for?
I wrote a little addon to dired to automatically display readme files in directories if there is one. I use it all the time, autoloads with my dired. I also wrote an init file generator and manager that I use every day, as long as some small packages to cleanup org mode noise, summarized in org-view-mode. Generally I use elisp instead of bash to cleanup directories, batch rename files in some special folders according to some specific naming rules etc. I also wrote an elisp script to re-build emacs, lots of other small stuff I haven't published on my github. You can check here some small extras I wrote or adapted from others for my personal use.
-
vanish.el: hide parts of a buffer
If you need some example of using text properties, here is some of my code, not sure if it is very good example, but it is very short and hopefully easy to understand. Here is a bit more elaborated one, and here is a bit of unorthodox usage of Emacs, also using text properties to achieve the effect. I don't recommend anything for "stable" system, beside org-view-mode, rest are just experiments and idea tests.
- Orgmode: Hide leading chars `#+`
-
Org-view-mode with new 'quick-edit' feature is now available from Melpa
For the usage info, check the README file in the Github repository.
-
Display README files in Dired buffer similar as on GitHub/GitLab
I have just reworked dired-auto-readme, fixed some bugs and made it aware of org-view-mode, so now it is possible to see readme files written in org mode without markup in Dired buffers. For example, here is a screenshot of org-tree-slide package by T. Ishikawa, cloned from his GitHub repo.
-
Pretty rendering of paragraphs with org-view mode
My attempt at pretty rendering paragraphs in org-mode: aligned vertically to left, right, middle and displayed with custom fonts.
-
[Pretty paragraph rendering with org-view mode](https://github.com/amno1/org-view-mode/blob/main/images/paragraphs.png)
I have been hacking last weekend on my org-view mode. It can now prettify quotes, verses and centered paragraphs by applying alignment and custom faces. It should now also work in older versions than the current master :).
-
Set initial visibility by tag
You can write your own minor mode, or just simply iterate through all headings with a given tag, and fold it in with-eval-after-load. You can check this code and see if it gives you an idea how to do it. Check part for tags; instead of setting invisible property for tag, you can fold your heading. Also match tags with specific keywords in them, not all tags as I do in regex.
What are some alternatives?
When comparing package-lint and org-view-mode you can also consider the following projects:
compat - COMPATibility Library for Emacs Lisp
org-modern - :unicorn: Modern Org Style
org-custom-cookies - An Emacs package that allows you to create custom cookies in org-mode
org-project - Capture TODOs for project using org-mode
dired-auto-readme - An Emacs package to automatically display a README file when one is present in a dired buffer.
dired-show-readme
generators - Functions to generate data structures
emacs-format-all-the-code - Auto-format source code in many languages with one command
obvious.el - Who needs comments when the code is so obvious
range-pattern - Range pattern for pcase
emacs-relocate-docs
package-lint vs compat
org-view-mode vs org-modern
package-lint vs org-custom-cookies
org-view-mode vs org-project
package-lint vs dired-auto-readme
org-view-mode vs dired-show-readme
package-lint vs generators
org-view-mode vs emacs-format-all-the-code
package-lint vs obvious.el
org-view-mode vs dired-auto-readme
package-lint vs range-pattern
org-view-mode vs emacs-relocate-docs