[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
From: |
Noam Postavsky |
Subject: |
bug#24616: 26.0.50; No backtrace when emacsclient --eval fails |
Date: |
Tue, 4 Oct 2016 16:52:29 -0400 |
On Tue, Oct 4, 2016 at 12:30 PM, Philipp Stephani <p.stephani2@gmail.com> wrote:
>
> Start the server.
> Then run e.g.
>
> $ emacsclient --eval '(progn (defun f () (error "foo")) (setq debug-on-error
> t) (f))'
> *ERROR*: foo
>
> Note that there's no backtrace. This makes it almost impossible to debug
> problems when using emacsclient.
>
Just a note: you can get a backtrace by setting debug-on-signal
instead of debug-on-error.
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Philipp Stephani, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails,
Noam Postavsky <=
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Clément Pit--Claudel, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Noam Postavsky, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Clément Pit--Claudel, 2016/10/04
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/05
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, npostavs, 2016/10/22
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Eli Zaretskii, 2016/10/22
- bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, npostavs, 2016/10/22
bug#24616: 26.0.50; No backtrace when emacsclient --eval fails, Live System User, 2016/10/23