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, 4 Oct 2017 10:19:07 -0400 [thread overview]
Message-ID: <CAM-tV-_V=Q5VvVk9ibBkecGR98jCjLp8rCFN==rzQZodmZDQCA@mail.gmail.com> (raw)
In-Reply-To: <874lrfatm6.fsf@aol.com>
On Wed, Oct 4, 2017 at 10:13 AM, Live System User <nyc4bos@aol.com> wrote:
>> 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.
Does setting debug-on-message set to "Text is read-only" help?
Or with debug-on-signal set to t? (You might have to continue ('c' in
the *Backtrace* buffer) if you hit some unrelated errors that are
normally suppressed)
next prev parent reply other threads:[~2017-10-04 14:19 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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM-tV-_V=Q5VvVk9ibBkecGR98jCjLp8rCFN==rzQZodmZDQCA@mail.gmail.com' \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).