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

From: Noam Postavsky <[email-masked]>
Date: Sun, 15 Oct 2017 15:48:54 -0400

Live System User <[email-masked]> writes:

>       Here is some GDB info.

> (gdb) bt
> #0  text_read_only (propval=propval@entry=XIL(0xb010))
>     at ../../src/textprop.c:71

> Lisp Backtrace:
> "eshell-write-history" (0x5642bf38)
> "run-hooks" (0x5642c020)
> "eshell-kill-buffer-function" (0x5642c200)
> "kill-buffer" (0x5642c400)
> "funcall-interactively" (0x5642c3f8)
> "call-interactively" (0x5642c660)
> "command-execute" (0x5642c808)

Thanks, my guess is you have some string with a read-only property in
eshell history (probably introduced by copying from another buffer), and
this is tripping up eshell-write-history.

Can you post the result of

    M-x pp-eval-expression RET eshell-history-ring RET

If my guess is correct there should be some strings of the form

    #("some command" 0 11 (read-only t))