GNU bug report logs - #28700
25.2; Cannot kill Eshell buffer

Previous Next

Package: emacs;

Reported by: Live System User <nyc4bos <at> aol.com>

Date: Wed, 4 Oct 2017 09:58:01 UTC

Severity: minor

Tags: fixed, patch

Merged with 29153

Found in versions 25.2, 25.3

Fixed in version 26.1

Done: Noam Postavsky <npostavs <at> users.sourceforge.net>

Bug is archived. No further changes may be made.

Full log

Message #14 received at 28700 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Live System User <nyc4bos <at> aol.com>
Cc: 28700 <at> debbugs.gnu.org
Subject: Re: bug#28700: 25.2; Cannot kill Eshell buffer
Date: Wed, 4 Oct 2017 10:19:07 -0400

On Wed, Oct 4, 2017 at 10:13 AM, Live System User <nyc4bos <at> aol.com> 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)
This bug report was last modified 7 years and 204 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.