Get the latest tech news
Inline previous result in Emacs Lisp
Álvaro Ramírez Inline previous result and why you should edebug Artur Malabarba's Debugging Elisp Part 1: Earn your independence is nearly a decade old, yet it rings just as true today. Learning to Edebug really "is the right decision for anyone who doesn't know how to Edebug." Why, you may ask? He best puts it as "running into errors is not only a consequence of tinkering with your editor, it is the only road to graduating in Emacs." For me personally, it earned me that independence to bend Emacs my way.
I wanted to minimize the eye jumping experience, so I figured I could likely bend things my way and print the result at point. At that point, I could have set a breakpoint in edebug-next-mode and eventually step into the relevant code, but hey we had a better clue. adviced:edebug-compute-previous-result removes "Result:" in addition to dropping(eval-expression-print-format previous-value), which I don't typically rely on.
Or read this on Hacker News