[email protected] (Adam Sjøgren) writes: > Christoph writes: > >> Maybe... In order to debug this, it would be useful to examine the >> various steps that lie between pressing C-c C-c and storing the >> message. Is "Edebug" the way to go? > > edebug-defun is my go-to (but I am no expert in the topic :-))
What I would do is first find the chain of function calls that sends a message, and then pick a likely one for edebugging. I started looking at this yesterday: I thought `message-fix-before-sending' sounded a likely culprit, but it wasn't to blame. That's as far as I got. _______________________________________________ info-gnus-english mailing list [email protected] https://lists.gnu.org/mailman/listinfo/info-gnus-english
