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: Wed, 04 Oct 2017 07:56:45 -0400 [thread overview]
Message-ID: <87y3orceiq.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87fuazb5hb.fsf@aol.com> (Live System User's message of "Wed, 04 Oct 2017 05:57:20 -0400")
Live System User <nyc4bos@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?
next prev parent reply other threads:[~2017-10-04 11:56 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 [this message]
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
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=87y3orceiq.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.