Replies: 1 comment 1 reply
-
|
Hey @shipmints Well, accepted patches are not longer part of this repository / latest builds. As of Emacs 31 we have only 3 patches:
Personally, I never proposed these patches to the upstream, mostly because upstream doesn't care much about mac-only features and lack of time/motivation. I am not following the devel mailing list, so can't say if any of these patches were ever discussed. I don't mind if someone proposes them to the upstream. AFAIR I have signed documents with FSF (so first two patches can be merged without any issues), but not sure about Nicolas G. Querol. |
Beta Was this translation helpful? Give feedback.
-
|
My recent experience sitting on (and occasionally contributing) to emacs-devel and bug-gnu-emacs suggests that people are indeed eager to improve macOS as a primary Emacs platform. People seem very approachable and since these patches are in the wild and you can probably estimate their uptake / number of users, that might help the maintainers understand the positive impact of these patches. If the patches are truly esoteric, I can imagine some discussion; e.g., yabai use case, BUT if the change is actually beneficial in general to all macOS users, which this one might very well be, it seems like it's worth the effort. |
Beta Was this translation helpful? Give feedback.
-
@jimeh has adopted the patches from this repo in his very nice (and now nix-based) builds over at
https://github.com/jimeh/emacs-builds and https://github.com/jimeh/build-emacs-for-macos
Per jimeh/emacs-builds#36 we'd like to understand the status of the very good patch set in upstream Emacs. Does anyone know the status of each patch, if it was ever submitted, if it was rejected (and why), if it was accepted but still in the queue (and who is assigned). Perhaps we can help with upstream adoption. We've seen several very good mac/NS patches collaborated on and accepted in recent times.
TIA,
-Stephane
Beta Was this translation helpful? Give feedback.
All reactions