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 #11 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 10:13:37 -0400

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

> Live System User <nyc4bos <at> aol.com> writes:
>
>> Hi,
>>
>>         I cannot kill an Eshell buffer.
>>
>>         When I attekpt to kill it either by `(kill-buffer)`
>>         "C-x k" or `(save-buffers-kill-terminal)` "C-x C-c"
>>         I get the error:
>>
>>               run-hooks: Text is read-only
>>
>>         `kill-buffer-hook` is:
>>         
>> kill-buffer-hook is a variable defined in ‘files.el’.
>> Its value is (t eshell-kill-buffer-function)
>> Local in buffer *eshell*; global value is 
>> (tramp-delete-temp-file-function uniquify-kill-buffer-function vc-kill-buffer-hook)
>
> 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.

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