Psionic K
Psionic K
These require makunbound to be redefined on module reloading. We can define a custom module unloader. While some programs may enjoy this convention, the usual case for development is that...
There are easier ways, but I found this in a stash # Manual definition for non-melpa package (epkgs.melpaBuild { pname = "melpazoid"; version = "0.0.0"; commit = "c7cc28607236aba92949e7c47ffb5affb03d6111"; packageRequires =...
## Includes indirection Jumping to an include statement in org mode is kind of annoying, indirection. Can probably make these live links. (org customization) ## Org Setup File Probably Needed...
https://emacs-eldev.github.io/eldev/#setup-procedure Jealous :cat: Probably want to CI integrate to create some machine commits when inputs are edited. This is basically human-in-the-loop since it's post-PR - badge for job - autogenerate...
https://github.com/leotaku/elisp-check/blob/master/elisp-check.el Likely some useful bits in there. Nice that it's an action.
Some commands seem likely to get renamed For consistency with elisp terms, I'm changing project -> package or feature, root-feature etc. Projectile is only in use to take advantage of...
https://github.com/positron-solutions/user-keys/actions/runs/5143521293/jobs/9258640515 Found this. Really wish for better linter exceptions. Too often, user knows better than linter. If I want to use `eval-after-load' in a package, I shouldn't have to give...
Some frequent schlep, aka meaningless unwanted work... You're developing along, everything works. Send package to CI, forget that it needs XYZ to build. Forget that Y is a MELPA package...
The emacs overlay exposed this cool function that might be good at running tests by inspecting the dependencies rather than requiring the user to update them.
I'm still avoiding heavier packages that concern themselves with dependencies and sandboxing. Nix and CI do sandboxing and dependencies. A user can use Nix locally to reproduce that. It's only...