Subject: Re: bug#28700: 25.2; Cannot kill Eshell buffer

From: Live System User <[email-masked]>
Date: Wed, 04 Oct 2017 11:21:04 -0400

Noam Postavsky <[email-masked]> writes:

> On Wed, Oct 4, 2017 at 10:13 AM, Live System User <[email-masked]> wrote:
>>> Can you get a backtrace if you M-x toggle-debug-on-error RET?
>>
>>          Ufortunately no;
>>
>> debug-on-error is a variable defined in ‘C source code’.
>> Its value is t
>> Original value was nil
>>
>>
>>          Only that *Message* buffer imfomation.
>
> Does setting debug-on-message set to "Text is read-only" help?
> Or with debug-on-signal set to t? (You might have to continue ('c' in
> the *Backtrace* buffer) if you hit some unrelated errors that are
> normally suppressed)

  Unfortunately, no ro both:
  
debug-on-message is a variable defined in ‘C source code’.
Its value is "Text is read-only"

debug-on-signal is a variable defined in ‘C source code’.
Its value is t
Original value was nil

         Only the "run-hooks: Text is read-only" message
         in the *Message* buffer appears.

         Thanks.