Replies: 1 comment 2 replies
-
|
I mean, you can always fork Emacs core or an installed package. You have just have to maintain a lot more dedication, since you'd have to recompile Emacs core and/or switch package managers so that your packages can be manipulated with Git and/or keep a manual list of all the patches you applied and ensure you re-apply them every time you upgrade something or switch machines.
|
Beta Was this translation helpful? Give feedback.
-
Nowadays with declarative build systems like
Why manual? I don't see why it couldn't be scripted together with whatever commands one runs to fetch and/or compile and install Emacs. Summarizing your comment: you are detailing and emphasizing something very similar to my "lower barrier to entry for most users" point. Is this summary correct? If so, are there no other advantages that you have thought of? PS: To be clear; I do think the three advantages I mentioned are quite significant; thanks for |
Beta Was this translation helpful? Give feedback.
-
|
If you use a package manager like Nix, then yeah, maybe it would be easier to maintain a fork of Emacs and/or various packages. Without that, it's a lot of manual work to make sure everything keeps working. I personally don't really know anything about this because I don't use any of those package managers. If you have tooling set up to make it trivial to fork the upstream, then of course you can do whatever you want. The point of |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have thought of only these (are there more?):
(eval `(el-patch-defun ,@(my-dynamic-computation)))requires user-intervention in (far?) fewer situations as it is resillient to e.g. most refactors where a patched definition is moved to another file
has lower barrier to entry for most users
N.b. the el-patch use-case of just validating that a definition form is as you expect (i.e. without any modifications e.g.
el-patch-add) can be done withgit apply --check(with a patch that modifies all lines you want to check).Maybe a discussion about this should be in the
README.md;git applyoffers an advantage in that it can be used with a much larger variety of software; helping users factor that in when considering usingel-patchmay be a net positive.Beta Was this translation helpful? Give feedback.
All reactions