Skip to main content
added 61 characters in body
Source Link
Drew
  • 79.1k
  • 10
  • 123
  • 257

Nope. There is no simple solution ready-to-hand. As far as I know, users just manually remove the bytecode from backtraces they report. That's what I do, at least.

This has been requested more than once, including with Emacs bug #6991.

The bug was summarily closed immediately -- no reason given. Eventually it was reopened and relegated to the "wishlist".

(You can always try again -- M-x report-emacs-bug, now that there is a new GNU Emacs maintainer. Dunno whether that will make a difference.)

Nope. There is no simple solution ready-to-hand. As far as I know, users just manually remove the bytecode from backtraces they report. That's what I do, at least.

This has been requested more than once, including with Emacs bug #6991.

The bug was summarily closed immediately -- no reason given.

(You can always try again -- M-x report-emacs-bug, now that there is a new GNU Emacs maintainer. Dunno whether that will make a difference.)

Nope. There is no simple solution ready-to-hand. As far as I know, users just manually remove the bytecode from backtraces they report. That's what I do, at least.

This has been requested more than once, including with Emacs bug #6991.

The bug was summarily closed immediately -- no reason given. Eventually it was reopened and relegated to the "wishlist".

(You can always try again -- M-x report-emacs-bug, now that there is a new GNU Emacs maintainer. Dunno whether that will make a difference.)

Source Link
Drew
  • 79.1k
  • 10
  • 123
  • 257

Nope. There is no simple solution ready-to-hand. As far as I know, users just manually remove the bytecode from backtraces they report. That's what I do, at least.

This has been requested more than once, including with Emacs bug #6991.

The bug was summarily closed immediately -- no reason given.

(You can always try again -- M-x report-emacs-bug, now that there is a new GNU Emacs maintainer. Dunno whether that will make a difference.)