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 #23 received at 28700 <at> debbugs.gnu.org (full text, mbox):

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

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

> On Wed, Oct 4, 2017 at 11:21 AM, Live System User <nyc4bos <at> aol.com> wrote:
>>
>>   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.
>
> Hmm, can you eval each function in the hook value individually and see
> which gets the error then?
>
> M-: (tramp-delete-temp-file-function)
> M-: (uniquify-kill-buffer-function)
> etc.

        They all evaluate to nil

.
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.