From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29067@debbugs.gnu.org
Subject: bug#29067: 26.0.90; "Invalid client frame" when doing save-buffers-kill-terminal
Date: Mon, 30 Oct 2017 18:49:29 +0000 [thread overview]
Message-ID: <CAFyQvY3dSjnDbrCk=mU9UF73_vGFZYCZ08fAfhszKg05X52q1g@mail.gmail.com> (raw)
In-Reply-To: <83lgjstr6y.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On Mon, Oct 30, 2017 at 2:40 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> Please show a Lisp backtrace from this error.
>
Sorry, should have done that earlier; I just assumed it didn't hold any
information of value for this case.
Debugger entered--Lisp error: (error "Invalid client frame")
signal(error ("Invalid client frame"))
error("Invalid client frame")
server-save-buffers-kill-terminal(nil)
save-buffers-kill-terminal()
eval((save-buffers-kill-terminal) nil)
eval-expression((save-buffers-kill-terminal) nil nil 127)
funcall-interactively(eval-expression (save-buffers-kill-terminal) nil
nil 127)
call-interactively(eval-expression nil nil)
command-execute(eval-expression)
When I edebugged save-buffers-kill-terminal, I saw that (frame-parameter
nil 'client) was evaluating to non-nil as it was returning "Unprintable
entity". So it is executing the wrong clause of that if.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1579 bytes --]
next prev parent reply other threads:[~2017-10-30 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 17:10 bug#29067: 26.0.90; "Invalid client frame" when doing save-buffers-kill-terminal Kaushal Modi
2017-10-30 18:40 ` Eli Zaretskii
2017-10-30 18:49 ` Kaushal Modi [this message]
2017-10-31 8:41 ` martin rudalics
2017-11-01 13:32 ` Kaushal Modi
2017-11-01 13:40 ` Kaushal Modi
2017-11-01 13:51 ` Kaushal Modi
2017-11-01 17:43 ` martin rudalics
2017-11-01 18:52 ` Kaushal Modi
2017-11-02 9:51 ` 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='CAFyQvY3dSjnDbrCk=mU9UF73_vGFZYCZ08fAfhszKg05X52q1g@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=29067@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.