|
From: | npostavs |
Subject: | bug#6991: Please keep bytecode out of *Backtrace* buffers |
Date: | Mon, 26 Jun 2017 23:56:54 -0400 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) |
Stefan Monnier <monnier@IRO.UMontreal.CA> writes: > I wonder why we do that, tho: > the previous code didn't have a comment, so I'm left guessing that maybe > it's that we don't want to advertise as "will stop when exiting foo" > a function which we're exiting? I tried git-blame, but that code seems to have been like that since "initial revision" (1991). I think your guess sounds reasonable. Anyway, here are the updated patches.
0001-Operate-on-frame-list-instead-of-printed-backtrace.patch
Description: patch
0002-Improve-ert-backtrace-recording.patch
Description: patch
0003-Escape-control-characters-in-backtraces-Bug-6991.patch
Description: patch
0004-Don-t-redundantly-cl-print-arglist-in-function-docst.patch
Description: patch
0005-Hide-byte-code-in-backtraces-Bug-6991.patch
Description: patch
0006-Escape-NUL-bytes-in-X-selections-Bug-6991.patch
Description: patch
[Prev in Thread] | Current Thread | [Next in Thread] |