4 ms·
> help for some of the current Emacs developers to publish a "How to start hacking Emacs" documen 1. Find thing you don't like 2. M-x find-function RET functio
by quotemstr 13y ago
> help for some of the current Emacs developers to publish a "How to start hacking Emacs" documen
1. Find thing you don't like
2. M-x find-function RET function-to-fix RET
3. Hack hack hack (use C-M-x or M-x eval-buffer liberally; also, read about edebug)
4. Make diff relative to Emacs base code
5. Send diff to bug-gnu-emacs@gnu.org
What I love about hacking on Emacs is that it's so easy to find the bit of code responsible for a given feature and hack on that code in a running editor. There's nothing like it. If I'm using Firefox and don't like the address bar, I need to go dig through XUL, find the thing I don't like, and restart Firefox. Emacs? You just find the function and edit it right in the editor.
- aaronem 13y agoThank you, yes, it's not so much finding the code I need to modify that's the problem, as understanding how any given single thing fits into the Emacs C source as a whole. Hacking the Lisp side I don't really have a problem with -- but if I want to, for example, extend the MESSAGE primitive so that it can check a list of messages not to emit in the minibuffer, things get very hairy, very fast. A general overview of what's what, and where, in the C source, would be extremely useful, and I haven't had much luck finding anything like that in the source distribution or online. (And, yes, I have read etc/CONTRIBUTE, etc/DEBUG, and (Info)Elisp/GNU Emacs Internals/*. And I'm pretty sure doing what I'm talking about doing to MESSAGE would be a bad idea, because it'd require a call up into Lisp space every time the primitive gets called, which can be extremely frequent especially during initialization. But I know somebody who'd like to have that functionality available, and it seemed like a relatively simple place to start, until I tried actually doing it.)
- rbanffy 13y ago> There's nothing like it. Smalltalk. I once crashed my Squeak environment by making "true := false".