From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Live System User <nyc4bos@aol.com>
Cc: 28700@debbugs.gnu.org
Subject: bug#28700: 25.2; Cannot kill Eshell buffer
Date: Sun, 15 Oct 2017 15:48:54 -0400 [thread overview]
Message-ID: <87bml88a55.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87o9p8p6sn.fsf@aol.com> (Live System User's message of "Sun, 15 Oct 2017 15:09:12 -0400")
Live System User <nyc4bos@aol.com> 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))
next prev parent reply other threads:[~2017-10-15 19:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 9:57 bug#28700: 25.2; Cannot kill Eshell buffer Live System User
2017-10-04 11:56 ` Noam Postavsky
2017-10-04 14:13 ` Live System User
2017-10-04 14:19 ` Noam Postavsky
2017-10-04 15:21 ` Live System User
2017-10-04 16:42 ` Noam Postavsky
2017-10-04 18:27 ` Live System User
2017-10-04 18:32 ` Noam Postavsky
2017-10-04 19:50 ` Live System User
2017-10-04 19:56 ` Noam Postavsky
2017-10-04 22:12 ` Live System User
2017-10-04 23:48 ` Noam Postavsky
2017-10-15 19:09 ` Live System User
2017-10-15 19:48 ` Noam Postavsky [this message]
2017-10-15 22:02 ` Live System User
2017-10-16 2:20 ` Noam Postavsky
2017-10-21 19:51 ` Noam Postavsky
2017-10-15 19:29 ` Live System User
2017-10-05 8:09 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bml88a55.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=28700@debbugs.gnu.org \
--cc=nyc4bos@aol.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.