all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 14:32:36 -0400	[thread overview]
Message-ID: <CAM-tV-_TCJ7i78wdAvcbKvA4y6tD1FjvQtZzrcFW6gLCOUq1SQ@mail.gmail.com> (raw)
In-Reply-To: <87tvzeahuz.fsf@aol.com>

On Wed, Oct 4, 2017 at 2:27 PM, Live System User <nyc4bos@aol.com> wrote:
>
>         They all evaluate to nil

Hmm, so maybe the run-hooks is a red herring. Could you instrument
kill-buffer with edebug, and step through to find where the error
happens?





  reply	other threads:[~2017-10-04 18:32 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 [this message]
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=CAM-tV-_TCJ7i78wdAvcbKvA4y6tD1FjvQtZzrcFW6gLCOUq1SQ@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 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.